Jsf: paletteTransparencyType bug?

i have a jsf problem ive been trying to solve for hours
now.....i need to export images as 8 bit png's with alpha
transparency.
<code>
var ex = new ExportOptions();
ex.exportFormat = "PNG";
ex.colorMode = "indexed";
ex.paletteTransparencyType = "rgba";
fw.getDocumentDOM().setExportOptions(ex);
fw.exportDocumentAs(d, savePath, null);
</code>
when i run this script, my images get saved, but not with
transparency. the optimize palette says "No Transparency" no matter
what i set paletteTransparencyType to.
is this a bug, or am i doing something wrong.

yes, the canvas is tranparent.
i actually solved this, and found an error in the extending
fireworks documentation. after changing a few options in the
optimize palette, i took the history steps and converted them to
jsf to see what it was doing.
the documentation states that paletteTransparencyType is a
property of the ExportOptions object, when in fact it is not. the
correct property is paletteTransparency. wow....that had me
scratching my head for hours.
so the correct jsf would be:
<code>
var ex = new ExportOptions();
ex.exportFormat = "PNG";
ex.colorMode = "indexed";
ex.paletteTransparency = "rgba";
fw.getDocumentDOM().setExportOptions(ex);
fw.exportDocumentAs(d, savePath, null);
</code>
i submitted this to adobe last night.

Similar Messages

JSF editor Bug ?

Hi everybody i'm trying the new jdeveloper 10.1.3 with jsf support , and after use it sometime, i realize that the jsf editor is not synchronizing very well the components on the backing code with the jsp document , when the backing code class isn't compiling (and it's saved in this state). This is a terrible source of error when you don't know it ...
the question is , this is a normal behaviour or horrible bug ?

Thanks, but that's not what i mean, you modify the components in the property inspector, but you don't write the methods code on the property inspector.The problem is when that code isn't compiling, if you keep using the jsp design view, the backing bean stops being updated ... if you dont realize of this bug you got desync the view with the backing ... :S

Struts-faces & JSF commandLink bug in RI 1.1

Hello,
There was a bug with JSF, multiple forms and commandLink as discussed in thread: http://forum.java.sun.com/thread.jsp?thread=526788&forum=427.
This bug is now fixed for JSF h:form form type.
I personnally use Struts and JSF with the struts-faces JAR and this issue is still not fixed when you create a form using the s:form tag, in fact as long as there is a s:form on the page the commandLinks do not work the same way as first reported for pure JSF apps.
Will this be fixed anytime soon in the struts-faces library? I hope so because I do need it.
Thanks
Xav

hi,
i guess [email protected]
or
http://issues.apache.org/bugzilla/enter_bug.cgi?product=Struts
might be a better place for that.
regards.

JSF Converter - bug

When J associate my converter to HtmlDataTable(h:dataTable) in JSF(JSP) page in 'Design' tab appear problems:
1) in dataTable there isn't any column visable
2) everything below dateTable in same Panel Grid aren't visable
All this affect only 'Design' tab. In 'Source' tab everything is OK and when J run application everithing work like it should.
Is this bug or can be fixed somehow?

Hi.
J solve the problem partly and here is the problem and solution:
Problem - JDeveloper 10.1.3 have problem in showing table when code look like this:
<h:dataTable width="350" value="#{infoBean.popular}" var="popular_">
<h:column>
<f:facet name="header">
<h:panelGroup>
<h:commandLink action="POPULAR">
<h:outputText value="Najpopularnije"/>
</h:commandLink>
</h:panelGroup>
</f:facet>
<h:commandLink>
<h:outputText value="#{popular_}" converter="ProductTitle"/>
</h:commandLink>
</h:column>
</h:dataTable>
Solution - When J change code to this 'Design' tab shows the table but not the text in 'outputText'(here #{popular_}):
<h:outputText value="#{popular_}">
<f:converter converterId="ProductTitle"/>
</h:outputText>
Please try this!

JDev JSF Reformatter Bug

Hi all,
Been meaning to post about this for some time but never found the time :-)
Using JSF, if I have an outputText with the escape attribute set to false and the value set to &nbsp; (because I want to put a non breaking space on my page) everything is great until I reformat the JSP. Upon reformatting, the &nbsp; is replaced with a normal space, and JDev complains of a malformed input character on that line in the JSP.
The system is still usable, although the nbsp doesn't show in the output page of course.
Just a minor annoyance ;-)
Ta,
Steve.

We're tracking this via bug ID 2789824 - if you have a support contract, this is visible on http://metalink.oracle.com.
Thanks,
Brian
JDev Team

JSF JSP Bug

The JSF JSP Wizard has a bug.
1. Select File>New>Web Tier>JSF>JSF JSP.
2. Click on Next. Specify file anme. Click on Next.
3. Automatically Expose UI Compoenents in a Existing Managed Bean radio button does not get selected.

A managed bean is the same as a backing bean except that the managed bean is managed by the JSF framework.
http://groundside.com/blog/DuncanMills.php?title=so_what_is_a_backing_bean&more=1&c=1&tb=1&pb=1
If a managed bean with a page binding is defined, the Automatically Expose UI Components in an Existing Managed Bean button does not become selectable.
The Automatically Expose UI Components in an Existing Managed Bean button should be selectable to check which managed beans have already been created.

JSF Questions...Please Help

Does anyone have any JSF web App example I can link to to get a feel
for the type of UIs that are available?
Also, Can you build a JSF Web Application without using JSP pages?
Finally, who has the most comprehensive JSF implementation?

You can take a look at the GlassFish admin GUI. It's new UI is done using JSF. If you install GlassFish it is under the lib/install/applications/admingui directory. It will soon be enabled by default, you may have to deploy it manually until this is done. It uses a very complete set of components.. the "Creator" component documentation covers most of these components.
https://glassfish.dev.java.net
ICEfaces has a good set of components (I don't have much experience w/ them yet). They've been around a while and are very expienced in JSF and Ajax:
http://www.icefaces.org
GlassFish app server provides the best "out of the box" environment for JSF. It includes JSF 1.2 and continues to update its version of JSF as bug fixes are available for JSF. If you're starting a new project, I highly recommend JSF 1.2 over 1.1.
For non-JSP JSF pages there are 2 choices that I am aware of:
Facelets: https://facelets.dev.java.net (created by Jacob Hookom)
JSFTemplating: https://jsftemplating.dev.java.net (created by me)
Facelets is an XHTML-based view framework that is much better and faster than JSP. It has good documentation and is well used.
JSFTemplating provides both XML and a JSF-specific format for defining JSF Views. It is also much better and faster than JSP. It's documentation needs improvement... I'm working on it. This framework includes many value added features like:
* Ability to create components using the template format
* page session
* events w/ handler support
* factory pattern for instantiating objects (eliminates need for writing custom components in many cases)
* @annotation support
* Interoperates with JSP
These all big features (that Facelets doesn't support) that I could elaborate much more on... but I won't now. :) JSFTemplating is mature and has been around for over 2 years (although it hasn't been Open Source for very long) -- some of it's core parts are even older. GlassFish's admin GUI uses it.
I hope this helps!
Ken Paulsen
https://jsftemplating.dev.java.net

Best practice for backing bean population? (also, ActionListener RANT)

Hello,
I am about 3/4 of the way through development of a small to medium size JSF application. Sometimes I really like JSF, but much of the time I am left puzzled or frustrated for hours trying to find workarounds to JSF's bugs/glitches and design flaws.
For example, early on, I was impressed with how easily it was to invoke a method from a page using an actionlistener. Now that I'm actually building things with JSF, the actionlistener funtionality still seems cool, but incredibly half baked. I find myself using request parameters LIKE CRAZY to work around the fact that JSF doesnt support passing parameters directly to backing bean methods. This feels awkward and wrong considering the fact that JSF is intended to abstract the HTTP underpinnings. To add insult to injury, I often have to iterate through ALL of the request parameters looking for one that has an id with an ending matching my desired property name (since JSF appends it's own crap to the beginning). I don't like doing things in a hacky way. This seems very hacky, and I feel dirty doing it.
So, my first question is, what is the best practice for populating backing beans??? How do others accomplish this. I can think of several other approaches, but none feel less hacky.
Second, are there plans in the next spec (please say there are) to allow parameters to be passed to backing bean methods? If not, WHY THE HECK NOT?
Even though JSF expert group people have been conspicuously absent from this forum of late, I'd really appreciate responses from you as well.
Thank you for your thoughts.

Hi BrownBear,
I've been using JSF for about 6 months now and I'd be glade to help as much as I can.
Concerning parameters, I'm not sure what your issue is but I use the f:param tag to pass them. If you could post an example of what you are trying to do, I could see exactly what your issue is. Maybe the f:param can't help you.
As for best practice for populating backing beans, I personaly try to let JSF do as much as possible. For example, if I have a backing bean with five properties, I make sure that they all are on the JSP page the bean serves. If one of the property is just there as an Id like, lets say, a Person ID (DB row key), then I put it on my JSP page as a hidden input field. I do the same with the properties that only for display, if I want them to be back in my bean when request comesback.
Hope this help some how. Please, feel free to ask specific questions related to your specific problem and I monitor this post and trnasfer to you the ;little JSF experience I have.
I'm pretty happy with JSF as it is but it sure needs improvements. :) What the heck, it's version 1.01 after all, and the next release should be a great one with the integration of JSTL.
Cheers

HOWTO : Portletizing Faces/EJB/Toplink onto Webcenter. Gotchas&Fixes

I thought I'd share some helpful links and tips.
If you develop ADF Faces portlets by the book you'll run into a couple of problems when trying to deploy them on the Standalone OC4J, and a couple more when deploying to Webcenter.
I followed the ADF tutorial here...
http://www.oracle.com/technology/obe/ADF_tutorial_1013/10131/index.htm
Chapter 11 contains info about some extra steps that you need to carry out in order to deploy onto Webcenter.
That chapter instructs you to create a Deployment Project, within which you create your deployment profile. That works well while you are deploying just the Faces/EJB/Toplink application. When you come to 'portletize' your JSF pages however, the deployment procedure seems to skip the WSRP/WSDL packaging step. You should be seeing this in the deployment output page.
"Creating WSDLs for the WSRP Application - WSDLs for the WSRP Application have been created"
It works OK if you create the ear deployment profile within your View Controller project - which contains the portlet.xml file.
See the Portletizing viewlet here
http://www.oracle.com/technology/products/webcenter/owcs_10132_demos.html
- they use the same deployment profile for both Faces and Portlet deployment - stored in the faces project.
When editing the portlet.xml file DefaultPage.view variable, miss out the "faces" part of the path to your initial JSF page - or you will get this error:-
"SEVERE: oracle.adf.model.portlet.binding.PortletBindingException"
See this thread...
Re: JSF Portlets Bug
Even if you have successfully deployed to Standalone OC4J, when you deploy to Webcenter you will get an error about "oracle.wsrp" shared library. Follow the advice on this thread to sort things out ...
Re: PDK with OC4J 10.1.3
Having successfully run my portletized Faces/Toplink pages served from Webcenter within a client JSF app in Jdeveloper, my next step is to deploy and run that portlet consumer on Webcenter.
So far I'm getting MDSRuntimeException when I access the expected url.
I believe I should look here next..
http://download-uk.oracle.com/docs/cd/B32110_01/webcenter.1013/b31074/jpsdg_deploy.htm#BIHFCJDD
I'll add more to this thread as I make more progress.
Good luck everyone!
Donald.

In the viewlet
http://www.oracle.com/technology/products/webcenter/owcs_10132_demos.html
the user is prompted for an 'MDS' location.
I didn't get that prompt. This problem is mentioned on another thread - the answer was to make sure the deployment profile being used was specifically a WebCenter deployment profile. I'm sure I didn't see that option in my "New..." list - until I shut down and restarted Jdeveloper. Exact name of profile type is "WebCenter Application WAR".
I have it now. Having been prompted for an MDS location (created an empty folder for this) when I deployed my portlet client to my standalone OC4J, at last the client app runs from standalone!
I think I still need to carry out some instructions from here
http://download-uk.oracle.com/docs/cd/B32110_01/webcenter.1013/b31074/jpsdg_deploy.htm#BIHFCJDD
in order to create a 'targeted EAR file' for deployment to WebCenter itself.
Message was edited by:
Mechos

Help needed with Logout Button

Hi all,
I have created a Java faces web application with some of the jsp pages in a protected folder. I am using Tomcat 4.1.24 form based authentication with a memoryRealm. This is all working fine.
I am now trying to create a logout button. I have created a button with an actionRef that invokes the following method:
public Action getLogoutAction() {
return new Action() {
public String invoke() {
FacesContext context = FacesContext.getCurrentInstance();
//Invalidate the session
HttpSession session = (HttpSession) context.getExternalContext().getSession(false);
if (session != null) {
session.invalidate();
return "logout";
This works. (I can no longer access the protected pages without re-entering the username and password.) However, rather than returning to the login page, I get a nasty HTTP status 500 error message. The 'root cause' is as follows:
java.lang.IllegalStateException: getAttribute: Session already invalidated
     at org.apache.catalina.session.StandardSession.getAttribute(StandardSession.java:954)
     at org.apache.catalina.session.StandardSessionFacade.getAttribute(StandardSessionFacade.java:171)
     at org.apache.catalina.session.StandardSessionFacade.getAttribute(StandardSessionFacade.java:171)
     at com.sun.faces.context.SessionMap.put(ExternalContextImpl.java:430)
etc etc....
I am not sure what this means. Can anyone help?
Patrick

Can you supply the rest of the stack trace? The "etc. etc." is what we need to see!
I believe this is a JSF RI bug - it looks like it doesn't deal with HttpSession invalidation.
The workaround is to remove the relevant objects from the session instead of invalidating, e.g.:
FacesContext context = FacesContext.getCurrentInstance();
context.getExternalContext().getSessionMap().remove("userInfo");
context.getExternalContext().getSessionMap().remove("otherThing");Or, even better, keep all of the per-session information that you'd need to chuck as child objects on whatever bean implements getLogoutAction(), so you could write:
public String invoke() {
this.userInfo = null;
this.otherThing = null;
}... which nicely hides any concerns with where or how your logged-in information is stored.
BTW, as a rule of thumb, calling any of getRequest(), getSession(), or getContext() on ExternalContext should be used a last resort. When you use these methods, you break encapsulation. (OTOH,
preserving encapsulation isn't more important than getting your application working.)
-- Adam Winer (EG member)

BUG - JSF InputText boxes not populating properly

Okay,
Here's the situation:
I have an edit page (JSF Web) that allows the user to pick an item to edit from a SelectOneMenu tag. When they pick the item the page rerenders and shows the object associated with the selected item allowing the user to edit the object in various InputText controls.
First of all the ValueChangeListener event doesn't work for the SelectOneMenu tag - the event is not recognized in the backing bean (with or without immediate set, the event code is never accessed.) - and so I had to tie the change to the pressing of a command button.
Upon pressing the command button, in the action event, I find the object from the selected item. Now I want to set the input text boxes in the screen to the various values of the object. There are two ways to do this. I either set the value property of the bound (using the binding property) backing bean to the objects property - the code looks like this:
<h:inputText binding="#{EditCalendarBean.name}"
value="#{EditCalendarBean.name.value}"/>
This results in a fatal error that halts the OC4J.
Alternatively; I added various properties to the backing bean one for each property of the object and bound the object's properties to these and then bound the user interface's value properties to the bean properties. For example, imagine a user interface control InputText tag called "name" has it's value property bound to a property on the bean called Name which returns String. This configuration runs but the InputText control when the page is re-rendered (after the submit), is empty even though I've set the value property. However, if I add an OutputText control to the page and bind it's value property to the same String property of the bean, the outputText control correctly shows the value of the object.
The code looks like this:

<h:inputText id="name" binding="#{EditCalendarBean.name}"
value="#{EditCalendarBean.nameValue}"/>
// Code in the Backing bean:
// Find the Bean from the submitted id from the SelectMenuTag.
CalendarData data = manager.getCalendarById(calendarID) ;
// Set value of the UITextInput components on the page.
this.getName().setValue(data.getName());
this.getDescription().setValue(this.getDescription());
// This results in a fatal error that halts the OC4J
// Method 2: declare two String properties on the bean and set them
// Then, in the page use the Value property of the InputText control.
// This runs but doesn't populate the controls. It does populate them if
// the contols are OutputText controls though!!!
this.setNameValue(data.getName());
this.setDescriptionValue(data.getDescription());
Best regards,
Nigel

Yes - this really is a bug. Any changes to make to the selectItems tag through the properties dialog rewrites the tag source code to seperate the selectOne tag and the selectItems tag. For example, before you use the dialog, you tag code could look like this:
<h:selectOneMenu binding="#{backing_showFactory.selectOneMenu1}"
id="selectOneMenu1">
<f:selectItems value="#{backing_showFactory.allFactories}"
binding="#{backing_showFactory.selectItems2}"
id="selectItems2"/>
</h:selectOneMenu>
After the use of the dialog the code will be rewritten as:
<h:selectOneMenu binding="#{backing_showFactory.selectOneMenu1}"
id="selectOneMenu1"/>
<f:selectItems value="#{backing_showFactory.allFactories}"
binding="#{backing_showFactory.selectItems2}"
id="selectItems2"/>
Notice, the tags are now seperated instead of the selectItems tag being encased in the selectOneMenu tag.

Bug in JSF 1.2 RI using in JDev 11g

Hi,
We have found a bug in the JSF RI version used by JDev 11g TP2:
In com.sun.faces.application.ApplicationImpl.createValidator, a MessageFormat is created using an erroneous pattern : created validator of type ''{0''}. This method is called by oracle.adfinternal.view.faces.util.rich.ConverterValidatorRegistrationUtils.addValidatorById. So, when the logging level is set to FINE, this crashes our application.
FYI, this seems to be corrected in the last version (1.2_06) of the JSF RI.
We tried replacing the jsf-api.jar and jsf-ri.jar files in lib\java\shared\oracle.jsf\1.2 with that new version but we are getting compilation errors in our JSPs.
Before we spend time trying to do that, can you please tell me if that sounds like the right thing to do (or if there is another solution). Also, can you please confirm that the subsequent versions of JDev will include a corrected version of the JSF RI.
Thanks.
Olivier

Hi,
the right place is JDeveloper/jsf-ri for JDeveloper. I'll file a bug
Frank

Bug in JSF 2?

I'm creating a fairly simple application using Weld and JSF2, running on Glassfish v3. However I have run into a problem which I can't get my head around. On one page I have a search field, which the result populates a h:selectOneMenu. From the h:selectOneMenu it should then be possible to select one of the results. This is were I get an error (or lack thereof, so to speak). The second request never reaches my RequestScoped bean, which I find odd.
I have created a very simple example to illustrate. The behavior I would expect, is the search field to be populated in the h:selectOneMenu, and then the value selected here shown in the bottom line.
If I change the bean to return a populated list for #{imTheBean.searchResult} on the first render, I'm able to submit just fine. Which is the behavior I was expecting from my example, but doesn't seem to work because I'm dynamically populating the searchResult..
<h:messages /> outputs: "searchform:searchResult: Validation Error: Value is not valid". Nothing shows in the glassfish log..
Am I doing something wrong, or is this a bug somewhere?
JSF page:
<?xml version="1.0" encoding="UTF-8"?>
<ui:composition xmlns="http://www.w3.org/1999/xhtml"
 xmlns:ui="http://java.sun.com/jsf/facelets"
 xmlns:f="http://java.sun.com/jsf/core"
 xmlns:h="http://java.sun.com/jsf/html">
 <h:messages/>
 <h:form id="searchform" styleClass="as_form">
 <h:inputText id="search" value="#{imTheBean.searchString}"/>
 <h:commandButton id="searchbutton" value="Search" action="#{imTheBean.doSearch}"/>
 
 
 <h:selectOneMenu id="searchResult" value="#{imTheBean.selectResult}">
 <f:selectItems value="#{imTheBean.searchResult}"/>
 </h:selectOneMenu>
 <h:commandButton id="selectButton" value="Select" action="#{imTheBean.doSelectResult}"/>
 </h:form>
 
 
 You selected #{imTheBean.selectedResult}
</ui:composition>Bean:
import java.io.Serializable;
import java.util.ArrayList;
import java.util.List;
import javax.enterprise.context.RequestScoped;
import javax.inject.Named;
* ImTheBean.
@RequestScoped
@Named
public class ImTheBean implements Serializable {
 private static final long serialVersionUID = -6412703392546135760L;
 private String searchString;
 private List<String> searchResult;
 private String selectResult;
 private String selectedResult;
 public void doSearch() {
 searchResult = new ArrayList<String>();
 searchResult.add(searchString);
 public void doSelectResult() {
 selectedResult = selectResult;
 public String getSearchString() {
 return searchString;
 public void setSearchString(String searchString) {
 this.searchString = searchString;
 public List<String> getSearchResult() {
 return searchResult;
 public void setSearchResult(List<String> searchResult) {
 this.searchResult = searchResult;
 public String getSelectedResult() {
 return selectedResult;
 public void setSelectedResult(String selectedResult) {
 this.selectedResult = selectedResult;
 public String getSelectResult() {
 return selectResult;
 public void setSelectResult(String selectResult) {
 this.selectResult = selectResult;
}

This is a vague error that has existed for a long time, also in JSF 1.x. If you search on that specific error in google you'll get many cries for help, with solutions.
Among other possibilities, it can happen when the list you use to fill the oneSelectMenu has different values on the postback; if the value that was selected in the menu does not exist in the backing list on the post back, you'll get this error.
Also check BalusC's reply in this thread:
[http://forums.sun.com/thread.jspa?forumID=427&threadID=5305443|http://forums.sun.com/thread.jspa?forumID=427&threadID=5305443]

BUG JSF h:dataTable with JDBC ResultSet - only last column is updated

I tried to create updatable h:dataTable tag with three h:inputText columns with JDBC ResultSet as data source. But what ever I did I have seceded to update only the last column in h:dataTable tag.
My JSF page is:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<%@ page contentType="text/html;charset=windows-1250"%>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
<f:view>
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=windows-1250"/>
<title>Stevan</title>
</head>
<body><h:form>

<h:messages/>


<h:dataTable value="#{tabela.people}" var = "record">
<h:column>
<f:facet name="header">
<h:outputText value="PIN"/>
</f:facet>
<h:inputText value="#{record.PIN}"/>
</h:column>
<h:column>
<f:facet name="header">
<h:outputText value="Surname"/>
</f:facet>
<h:inputText value="#{record.SURNAME}"/>
</h:column>
<h:column>
<f:facet name="header">
<h:outputText value="Name"/>
</f:facet>
<h:inputText value="#{record.NAME}"/>
</h:column>
</h:dataTable>

<h:commandButton value="Submit"/>
</h:form></body>
</html>
</f:view>
My java been is:
package com.steva;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
public class tabela {
private Connection conn;
private ResultSet resultSet;
public tabela() throws SQLException, ClassNotFoundException {
Statement stmt;
Class.forName("oracle.jdbc.OracleDriver");
conn = DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe", "hr", "hr");
stmt = conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE);
resultSet = stmt.executeQuery("SELECT PIN, SURNAME, NAME FROM PERSON");
public ResultSet getPeople() {
return resultSet;
I have instaled “Oracle Database 10g Express Edition Release 10.2.0.1.0” – product on my PC localy. I have enabled HR schema and I have instaled and pupulated with sample data folloving table:
CREATE TABLE "PERSON"
( "PIN" VARCHAR2(20) NOT NULL ENABLE,
 "SURNAME" VARCHAR2(30),
 "NAME" VARCHAR2(30),
 CONSTRAINT "PERSON_PK" PRIMARY KEY ("PIN") ENABLE
I have:
Windows XP SP2
Oracle JDeveloper Studio Edition Version 10.1.3.1.0.3894
I am not shure why this works in that way, but I think that this is a BUG
Thanks in advance.

Hi,
I am sorry because of formatting but while I am entering text looks fine but in preview it is all scrambled. I was looking on the Web for similar problems and I did not find anything similar. Its very simple sample and I could not believe that the problem is in SUN JSF library. I was thinking that problem is in some ResultSet parameter or in some specific Oracle implementation of JDBC thin driver. I did not try this sample on any other platform, database or programming tool. I am new in Java and JSF and I have some experience only with JDeveloper.
Java been(session scope):
package com.steva;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
public class tabela {
private Connection conn;
private ResultSet resultSet;
public tabela() throws SQLException, ClassNotFoundException {
Statement stmt;
Class.forName("oracle.jdbc.OracleDriver");
conn = DriverManager.getConnection
("jdbc:oracle:thin:@localhost:1521:xe", "hr", "hr");
stmt = conn.createStatement
(ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE);
resultSet = stmt.executeQuery("SELECT PIN, SURNAME, NAME FROM PERSON");
public ResultSet getZaposleni() {
return resultSet;
JSF Page:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<%@ page contentType="text/html;charset=windows-1250"%>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
<f:view>
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=windows-1250"/>
<title>Stevan</title>
</head>
<body><h:form>

<h:messages/>


<h:dataTable value="#{tabela.zaposleni}" var = "record">
<h:column>
<f:facet name="header">
<h:outputText value="PIN"/>
</f:facet>
<h:inputText value="#{record.PIN}"/>
</h:column>
<h:column>
<f:facet name="header">
<h:outputText value="Surname"/>
</f:facet>
<h:inputText value="#{record.SURNAME}"/>
</h:column>
<h:column>
<f:facet name="header">
<h:outputText value="Name"/>
</f:facet>
<h:inputText value="#{record.NAME}"/>
</h:column>
</h:dataTable>

<h:commandButton value="Submit"/>
</h:form></body>
</html>
</f:view>

BUG JSF Select Item not binding properly

Dear Oracle,
I'm running JDeveloper 10g version 10.1.3.0.3.3412 early access 1. If you create a HTMLMenu1 select list in a JSF Page and use the properties dialog to bind the values to a backing bean, the binding get's lost and the page doesn't call the value binding. What's more, if you try to rebind the values using the dialog, JDeveloper repeatedly inserts a new SelectItems tag for the menu.
For example, if you create the SelectMenu1 and then use the dialog to bind the selectItems to a backing bean property, you will end up with code something like this:
<h:selectOneMenu binding="#{backing_showFactory.selectOneMenu1}"
id="selectOneMenu1"
valueChangeListener="#{backing_showFactory.selectFactoryEvent}"/>
<f:selectItems value="#{backing_showFactory.allFactories}"
binding="#{backing_showFactory.selectItems1}"
id="selectItems1"/>
Now, click on the newly created menu item in the design window of the JSP editor and bring up the properties dialog. You will see that the value binding is blank. If you reenter the value binding information, JDeveloper creates a new tag so you end up with the following:
<h:selectOneMenu binding="#{backing_showFactory.selectOneMenu1}"
id="selectOneMenu1"
valueChangeListener="#{backing_showFactory.selectFactoryEvent}"/>
<f:selectItems value="#{backing_showFactory.allFactories}"
binding="#{backing_showFactory.selectItems2}"
id="selectItems2"/>
<f:selectItems value="#{backing_showFactory.allFactories}"
binding="#{backing_showFactory.selectItems1}"
id="selectItems1"/>
Each time you repeat the process, JDeveloper creates another tag:
<h:selectOneMenu binding="#{backing_showFactory.selectOneMenu1}"
id="selectOneMenu1"
valueChangeListener="#{backing_showFactory.selectFactoryEvent}"/>
<f:selectItems value="#{backing_showFactory.allFactories}"
binding="#{backing_showFactory.selectItems3}"
id="selectItems3"/>
<f:selectItems value="#{backing_showFactory.allFactories}"
binding="#{backing_showFactory.selectItems2}"
id="selectItems2"/>
<f:selectItems value="#{backing_showFactory.allFactories}"
binding="#{backing_showFactory.selectItems1}"
id="selectItems1"/>
Either way, if you clean up the JSF page with the spurious tags, the value binding (in the example above backing_showFactory.allFactories), is never called.

Yes - this really is a bug. Any changes to make to the selectItems tag through the properties dialog rewrites the tag source code to seperate the selectOne tag and the selectItems tag. For example, before you use the dialog, you tag code could look like this:
<h:selectOneMenu binding="#{backing_showFactory.selectOneMenu1}"
id="selectOneMenu1">
<f:selectItems value="#{backing_showFactory.allFactories}"
binding="#{backing_showFactory.selectItems2}"
id="selectItems2"/>
</h:selectOneMenu>
After the use of the dialog the code will be rewritten as:
<h:selectOneMenu binding="#{backing_showFactory.selectOneMenu1}"
id="selectOneMenu1"/>
<f:selectItems value="#{backing_showFactory.allFactories}"
binding="#{backing_showFactory.selectItems2}"
id="selectItems2"/>
Notice, the tags are now seperated instead of the selectItems tag being encased in the selectOneMenu tag.

Jsf: paletteTransparencyType bug?

Similar Messages

Maybe you are looking for