Bug in JCheckBox / bc4j boolean attribute

Hi,
I've got an attribute that is of type boolean. In the database, it's a NUMBER(1,0) field. In my jclient, I've used a JCheckBox with it's model set to the boolean field. I've chosen '0' for the false value and '1' for the true value.
If I create a new record in my application and click the commit button, it complains that the boolean field is required. If I then check the checkbox (which sets it internal value to 1 presumably) and then decheck it again (reset it to 0), I can commit without problems (now it sees 0 as value, which is not null, so it accepts that).
Why doesn't it accept the unchecked box right away?
(I could set the attribute to not-required, but I want to have 0 or 1 in the database, never null.)
Greetings,
Ivo

Hi,
I've got an attribute that is of type boolean. In the database, it's a NUMBER(1,0) field. In my jclient, I've used a JCheckBox with it's model set to the boolean field. I've chosen '0' for the false value and '1' for the true value.
If I create a new record in my application and click the commit button, it complains that the boolean field is required. If I then check the checkbox (which sets it internal value to 1 presumably) and then decheck it again (reset it to 0), I can commit without problems (now it sees 0 as value, which is not null, so it accepts that).
Why doesn't it accept the unchecked box right away?Values from the checkbox are updated on the row only on actionPerformed from the checkbox so that you can enter nulls for the bound attribute (if you do not perform any checkbox operations). In your case you need the checkbox bound value to be 'false' by default, then you may provide a default value of 0 for the 'attribute' on the Bc4J side.
(I could set the attribute to not-required, but I want to have 0 or 1 in the database, never null.)
Greetings,
Ivo

Similar Messages

  • File and boolean attribute on item

    Hi,
    I work with Oracle9iAS Portal PL/SQL API (9.0.2.6).
    I define an item type (CAID = 213/ ID = 37399) with several attributes. When I try to create/modify an item I have problems with boolean attributes and file attributes.
    In case of boolean attributes, I'm not able to set the value to true. I try with several values (IS_ON, True, 1) but the attribute is still set to false. Is there anything wrong with the value I assign to the attribute before creating the item ? When I try to create the item and then modifying the attribute, the value stay to false.
    For the file attributes, I use the upload_blob function inside wwsbr_api and the file appear in the wwdoc_document table. I set the file attribute value with the return value of the upload_blob function.
    When I call the add_item_post_upload, an error occurs (ORA-29532: Java call terminated by uncaught Java exception: java.lang.NullPointerException : -29532)
    Is this a bug or not ?
    Thanks Eddy.
    For help see my sample code below :
    (ID of attribute, page, region are correct. I also test each type of attribute separately)
    declare
    l_master NUMBER;
    l_store portal.wwsto_api_session;
    l_custom_attribute portal.wwsbr_type.array := portal.wwsbr_type.empty;
    l_custom_attribute_id portal.wwsbr_type.array := portal.wwsbr_type.empty;
    l_custom_attribute_caid portal.wwsbr_type.array := portal.wwsbr_type.empty;
    l_custom_attribute_data_type portal.wwsbr_type.array := portal.wwsbr_type.empty;
    l_str VARCHAR2(100);
    l_Blob BLOB;
    l_filename VARCHAR2(100);
    begin
    -- set context
    portal.wwctx_api.SET_CONTEXT('ctx','ctx01','');
    -- load a session (Allow use of set_Attribute ...)
    DBMS_OUTPUT.put_line('Load session');
    l_store := portal.wwsto_api_session.load_session('ctx','ctx');
    -- set parameters
    -- item type = 'Item_ed'
    l_store.set_attribute('ITEM_TYPE', 37399); -- Item type id
    l_store.set_attribute('ITEM_CAID', 213); -- Item type caid (page group owner of item type)
    l_store.set_attribute('PAGE_GROUP_ID', 213); -- Page group
    l_store.set_attribute('FOLDER_ID', 37179); -- Page within page group
    l_store.set_attribute('REGION_ID', 3216); -- Region id within page
    -- see wwv_user_corners to determine template of page
    -- see wwsbr_all_folder_regions for region display_name and region id (for template)
    -- Get date format to insert right date string
    SELECT DISTINCT value
    INTO l_str
    FROM v$nls_parameters
    WHERE parameter = 'NLS_DATE_FORMAT';
    dbms_output.put_line('date format ins : ' || l_str);
    -- define attributes (for example, id are hardcoded
    DBMS_OUTPUT.put_line('Define attributes');
    -- 1080 = PRODUCT_CODE
    l_custom_attribute(1) := 'MEHI';
    l_custom_attribute_id(1) := 1080;
    l_custom_attribute_caid(1) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(1) := 'text';
    -- 1081 = PRODUCT_AUTHOR
    l_custom_attribute(2) := 'ESTAT';
    l_custom_attribute_id(2) := 1081;
    l_custom_attribute_caid(2) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(2) := 'text';
    -- 1469 = LANGUAGE
    l_custom_attribute(3) := 'fr';
    l_custom_attribute_id(3) := 1469;
    l_custom_attribute_caid(3) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(3) := 'text';
    -- 3 = title
    l_custom_attribute(4) := 'title value';
    l_custom_attribute_id(4) := 3;
    l_custom_attribute_caid(4) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(4) := 'text';
    -- 50 = wwsbr_text_
    l_custom_attribute(5) := 'wwsbr_text_ value';
    l_custom_attribute_id(5) := 50;
    l_custom_attribute_caid(5) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(5) := 'text';
    -- 1464 = Release date
    l_custom_attribute(6) := TO_CHAR(TO_DATE('21-JAN-2004 10:00 AM', 'DD-MON-YYYY HH12:MI PM'),l_str);
    l_custom_attribute_id(6) := 1464;
    l_custom_attribute_caid(6) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(6) := 'date';
    -- 1108 = download
    l_custom_attribute(7) := 'http://www.oracle.com/';
    l_custom_attribute_id(7) := 1108;
    l_custom_attribute_caid(7) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(7) := 'url';
    -- 1485 = CDROM
    l_custom_attribute(8) := '1';
    l_custom_attribute_id(8) := 1485;
    l_custom_attribute_caid(8) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(8) := 'boolean';
    -- 1111 = PAGE_NB
    l_custom_attribute(8) := '1';
    l_custom_attribute_id(8) := 1111;
    l_custom_attribute_caid(8) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(8) := 'number';
    -- 1783 = COVER_IMAGE
    -- get image
    SELECT BANNER
    INTO l_Blob
    FROM metadata_tbl
    WHERE PRODUCT_CODE = 'caa10000';
    -- upload image in repository
    l_filename := portal.wwsbr_api.upload_blob('BANNERupload',l_Blob, 'image/pjpeg');
    DBMS_OUTPUT.put_line('filename : ' || l_filename);
    l_custom_attribute(9) := l_filename;
    l_custom_attribute_id(9) := 1783;
    l_custom_attribute_caid(9) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(9) := 'file';
    DBMS_OUTPUT.put_line('Insert item starts');
    l_master := portal.wwsbr_api.add_item_post_upload(
    p_caid => l_store.get_attribute_as_number('PAGE_GROUP_ID'),
    p_folder_id => l_store.get_attribute_as_number('FOLDER_ID'),
    p_display_name => 'Insert : MEHI',
    p_type_id => l_store.get_attribute_as_number('ITEM_TYPE'),
    p_type_caid => l_store.get_attribute_as_number('ITEM_CAID'),
    p_region_id => l_store.get_attribute_as_number('REGION_ID'), --to set or default
    p_display_option => portal.WWSBR_API.IN_PLACE,
    -- p_category_id in number default general_category,
    -- p_category_caid in number default shared_objects,
    -- p_perspectives in g_perspectiveidarray default g_perspectiveidemptyarray,
    -- p_perspectives_caid in g_caid_array default g_empty_caid_array,
    -- p_author in varchar2 default wwctx_api . get_user,
    -- p_image_name => l_filename,
    -- p_image_alignment in varchar2 default align_left,
    -- p_description in varchar2 default null,
    -- p_keywords in varchar2 default null,
    -- p_file_name =>l_filename, --in varchar2 default null,
    p_text => 'text field',
    -- p_url in varchar2 default null,
    -- p_plsql in varchar2 default null,
    -- p_plsql_execute_mode in varchar2 default null,
    -- p_plsql_execute_user in varchar2 default null,
    -- p_folderlink_id in number default null,
    -- p_folderlink_caid in number default null,
    -- p_publish_date in varchar2 default null,
    -- p_expire_mode in varchar2 default permanent,
    -- p_expiration in varchar2 default null,
    -- p_master_item_id in number default null,
    -- p_hide_in_browse in number default no,
    -- p_checkable in number default no,
    -- p_parent_item_id in number default 0,
    p_attribute_id => l_custom_attribute_id,
    p_attribute_caid => l_custom_attribute_caid,
    p_attribute_data_type => l_custom_attribute_data_type,
    p_attribute_value => l_custom_attribute
    DBMS_OUTPUT.put_line('Insert item ends. Item identifier : ' || l_master);
    -- Invalidate cache from SQLPLUS
    portal.wwpro_api_invalidation.execute_cache_invalidation;
    DBMS_OUTPUT.put_line('Cache invalidated');
    -- Drop session
    portal.wwsto_api_session.drop_session('ctx','ctx');
    -- Clean context
    portal.wwctx_api.clear_context;
    COMMIT;
    exception
    WHEN portal.wwctx_api.AUTHENTICATION_EXCEPTION THEN
    DBMS_OUTPUT.PUT_LINE('AUTHENTICATION_EXCEPTION : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.CANNOT_INSERT_DOCUMENT THEN
    DBMS_OUTPUT.PUT_LINE('CANNOT INSERT DOCUMENT : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.DUPLICATE_FOLDER THEN
    DBMS_OUTPUT.PUT_LINE('DUPLICATE_FOLDER : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.DUPLICATE_ID THEN
    DBMS_OUTPUT.PUT_LINE('DUPLICATE_ID : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.DUPLICATE_NAME THEN
    DBMS_OUTPUT.PUT_LINE('DUPLICATE_NAME : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.FOLDER_VERSIONING_IS_AUDIT THEN
    DBMS_OUTPUT.PUT_LINE('FOLDER_VERSIONING_IS_AUDIT : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.FOLDER_VERSIONING_IS_NONE THEN
    DBMS_OUTPUT.PUT_LINE('FOLDER_VERSIONING_IS_AUDIT : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.ILS_DISABLED THEN
    DBMS_OUTPUT.PUT_LINE('ILS_DISABLED : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.ILS_DISABLED_FOR_ITEM THEN
    DBMS_OUTPUT.PUT_LINE('ILS_DISABLED_FOR_ITEM : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_CAID THEN
    DBMS_OUTPUT.PUT_LINE('INVALID CAID : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_CATEGORY THEN
    DBMS_OUTPUT.PUT_LINE('INVALID CATEGORY : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_EXPIRE_DATE THEN
    DBMS_OUTPUT.PUT_LINE('INVALID_EXPIRE_DATE : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_EXPIRE_DATE_FORMAT THEN
    DBMS_OUTPUT.PUT_LINE('INVALID_EXPIRE_DATE_FORMAT : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_EXPIRE_NUMBER THEN
    DBMS_OUTPUT.PUT_LINE('INVALID_EXPIRE_NUMBER : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_FOLDER THEN
    DBMS_OUTPUT.PUT_LINE('INVALID_FOLDER : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_FOLDER_ID THEN
    DBMS_OUTPUT.PUT_LINE('INVALID FOLDER ID : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_ITEM_ID THEN
    DBMS_OUTPUT.PUT_LINE('INVALID ITEM ID : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_ITEMTYPE THEN
    DBMS_OUTPUT.PUT_LINE('INVALID ITEMTYPE : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_MOVE THEN
    DBMS_OUTPUT.PUT_LINE('INVALID MOVE : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_NAME THEN
    DBMS_OUTPUT.PUT_LINE('INVALID NAME : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_NUMBER THEN
    DBMS_OUTPUT.PUT_LINE('INVALID NUMBER : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_PERSPECTIVE THEN
    DBMS_OUTPUT.PUT_LINE('INVALID PERSPECTIVE : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_PLSQL_EXECUTE_USER THEN
    DBMS_OUTPUT.PUT_LINE('INVALID_PL/SQL_EXECUTE_USER : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_PUBLISH_DATE_FORMAT THEN
    DBMS_OUTPUT.PUT_LINE('INVALID_PUBLISH_DATE_FORMAT : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_PUBLISH_DATE_VALUE THEN
    DBMS_OUTPUT.PUT_LINE('INVALID_PUBLISH_DATE_VALUE : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_USERNAME THEN
    DBMS_OUTPUT.PUT_LINE('INVALID USERNAME : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.ITEM_CREATION_ERROR THEN
    DBMS_OUTPUT.PUT_LINE('ITEM_CREATION ERROR : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.ITEM_NOT_FOUND_ERROR THEN
    DBMS_OUTPUT.PUT_LINE('ITEM NOT FOUND ERROR : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.ITEM_UPDATE_ERROR THEN
    DBMS_OUTPUT.PUT_LINE('ITEM_UPDATE_ERROR : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.MISSING_DISPLAY_NAME THEN
    DBMS_OUTPUT.PUT_LINE('MISSING DISPLAY NAME : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.MISSING_ITEM_TYPE THEN
    DBMS_OUTPUT.PUT_LINE('MISSING ITEM TYPE : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.MISSING_NAME THEN
    DBMS_OUTPUT.PUT_LINE('MISSING NAME : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.MISSING_PLSQL_EXECUTE_USER THEN
    DBMS_OUTPUT.PUT_LINE('MISSING plsql execute user : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.NAME_TOO_LONG THEN
    DBMS_OUTPUT.PUT_LINE('name too long : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.NO_ITEM_REGION THEN
    DBMS_OUTPUT.PUT_LINE('not item region : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.NO_MASTER_ITEM_ID THEN
    DBMS_OUTPUT.PUT_LINE('no master item id : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.NOT_ENOUGH_PRIVS THEN
    DBMS_OUTPUT.PUT_LINE('not enough privs : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.NULL_EXPIRE_DATE THEN
    DBMS_OUTPUT.PUT_LINE('null expire date : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.NULL_EXPIRE_NUMBER THEN
    DBMS_OUTPUT.PUT_LINE('null expire number : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.PERMISSION_DENIED THEN
    DBMS_OUTPUT.PUT_LINE('permission denied : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.PLSQL_REQUIRED THEN
    DBMS_OUTPUT.PUT_LINE('plsql required : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.QUOTA_EXCEEDED THEN
    DBMS_OUTPUT.PUT_LINE('quota exceeded : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.REQD_ATTR_MISSING THEN
    DBMS_OUTPUT.PUT_LINE('reqd attr missing : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.UNKNOWN_ERROR THEN
    DBMS_OUTPUT.PUT_LINE('unknown error : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.URL_REQUIRED THEN
    DBMS_OUTPUT.PUT_LINE('url required : ' || sqlerrm);
    ROLLBACK;
    when OTHERS then
    DBMS_OUTPUT.PUT_LINE('OTHERS : ' || sqlerrm || ' : ' || sqlcode);
    ROLLBACK;
    end;

    Hi Eddy:
    On Friday, we put in a TAR with Oracle support about the identical problem. When editing an item using the API, the boolean attributes always reset. The values of the boolean attributes aren't even being changed. The only reason we need to set them again is the limitation of the API where you have to feed all attributes back in.
    So far, Oracle has said it sounds like a bug and they want to know the exact sequence of steps to repeat it.
    Rgds/Mark M.
    Portal 9.0.2.6

  • Problem with boolean attribute of JSP tag

    Hi,
    I've being trying to use a custom JSP tag, which has a boolean attribute, declared in the TLD as follows:
    <attribute>
    <name>checked</name>
    <required>false</required>
    <rtexprvalue>true</rtexprvalue>
    <type>boolean</type>
    </attribute>
    The JSP code snippet is:
    <ui:check checked="<%= myBean.isChecked() %>"/>
    where myBean.isChecked() returns a boolean value (primitive type).
    It works fine on some web containers, but it causes a JSP compilation error on Oracle9iAS 9.0.3 Java Edition, which looks like the following:
    Method toBoolean(boolean) not found in class test. _jsp_taghandler_57.setChecked( OracleJspRuntime.toBooleanObject( toBoolean( myBean.isChecked())));
    After decompiling the container's JSP parser, I found what I think it's a bug. The java class generated by the JSP parser does not define a toBoolean method, and neither do its superclasses. The method is defined on the OracleJspRuntime class! I think the correct code would have to be something like:
    OracleJspRuntime.toBooleanObject(OracleJspRuntime.toBoolean(...))
    If I'm correct, then the "convertExpression" method of the "oracle.jsp.parse.JspUtils" class must be changed, because it outputs such wrong code for not just boolean types, but for all the primitive types.
    So, has anyone ever faced this problem before? Does it have a workaround, or a patch? Is it included on the bug fixes for the 9.0.4 release?
    Thanks!

    Instead of:
    out.println("<body onload ="+strAlert+">");
    Try this:
    out.println("<body onload =\""+strAlert+\"">");
    Add two \" around the alert call.

  • Boolean attribute on a domain

    I'm trying to use a BC4J that has a Boolean attribute.
    The domain is defined as:
    MyDomain
    Attribute JavaType OracleType
    String1 String varchar2(30)
    String2 String varchar2(30)
    Boolie1 Boolean Number()
    Creation of BC4J objects and forward generation of the Oracle Object Type and a table using it as an attribute work just fine.
    The problem arises when committing:
    ThingVO doc = new ThingVO("a simple VO with some string attributes and a MyDomain attribute");
    MyDomain myd = new MyDomain();
    myd.setString1("stringy");
    myd.setString2("thingy");
    myd.setBoolie(Boolean.TRUE);
    doc.setMyDomain(acl);
    am.commit();
    produces:
    [207] java.sql.SQLException: Unable to convert object to oracle.sql.Datum: true
         at oracle.jpub.runtime.Util.convertToOracle(Util.java:169)
         at oracle.jpub.runtime.MutableStruct.getDatumAttribute(MutableStruct.java:247)
         at oracle.jpub.runtime.MutableStruct.getDatumAttributes(MutableStruct.java:264)
         at oracle.jpub.runtime.MutableStruct.toDatum(MutableStruct.java:91)
         at oracle.jpub.runtime.MutableStruct.toDatum(MutableStruct.java:99)
         at oracle.jbo.domain.Struct.toDatum(Struct.java:456)
         at oracle.jbo.domain.Struct.toDatum(Struct.java:422)
         at oracle.jdbc.driver.OraclePreparedStatement.setCustomDatum(OraclePreparedStatement.java:2415)
         at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedStatement.java:2900)
         at oracle.jbo.server.OracleSQLBuilderImpl.bindInsertStatement(OracleSQLBuilderImpl.java:1462)
         at oracle.jbo.server.EntityImpl.bindDMLStatement(EntityImpl.java:5586)
         at oracle.jbo.server.OracleSQLBuilderImpl.doEntityDML(OracleSQLBuilderImpl.java:343)
         at oracle.jbo.server.EntityImpl.doDMLWithLOBs(EntityImpl.java:4296)
         at oracle.jbo.server.EntityImpl.doDML(EntityImpl.java:4231)
         at oracle.jbo.server.EntityImpl.postChanges(EntityImpl.java:3410)
         at oracle.jbo.server.DBTransactionImpl.doPostTransactionListeners(DBTransactionImpl.java:2274)
         at oracle.jbo.server.DBTransactionImpl.postChanges(DBTransactionImpl.java:2216)
         at oracle.jbo.server.DBTransactionImpl.commitInternal(DBTransactionImpl.java:1511)
         at oracle.jbo.server.DBTransactionImpl.commit(DBTransactionImpl.java:1677)
    It looks like oracle.jpub.runtime.Util.convertToOracle isn't written to support Boolean attributes. Is that true?

    Here you go:
    PS: I forgot to mention before that I'm using the 9.0.3 preview. I tried the same thing in 9.0.2 and got little different error.
    package demo.common;
    import oracle.jbo.domain.DomainOwnerInterface;
    import oracle.jbo.domain.DomainInterface;
    import oracle.jbo.JboException;
    import oracle.sql.*;
    import oracle.jbo.domain.DatumFactory;
    import java.math.BigDecimal;
    import java.math.BigInteger;
    import java.sql.SQLException;
    import java.lang.String;
    import java.lang.Boolean;
    import oracle.jbo.StructureDef;
    import oracle.jbo.domain.Struct;
    import oracle.jbo.domain.DomainStructureDef;
    import oracle.jbo.domain.DomainAttributeDef;
    // --- File generated by Oracle Business Components for Java.
    public class ObjectTypeDomain extends Struct
    static CustomDatumFactory[] mCustDatFac = null;
    static int[] mSQLTypes = null;
    static DomainStructureDef mStructureDef = null;
    static CustomDatumFactory fac;
    public ObjectTypeDomain() throws SQLException
    public ObjectTypeDomain(Datum value) throws SQLException
    super(value);
    public static CustomDatumFactory getCustomDatumFactory()
    if (fac == null)
    class facClass implements CustomDatumFactory
    public CustomDatum create(Datum d, int sql_type_code) throws SQLException
    if (d != null)
    return new ObjectTypeDomain(d);
    return null;
    fac = new facClass();
    return fac;
    public int[] getAttrSQLTypes()
    if (mSQLTypes == null)
    mSQLTypes = buildAttrSQLTypes();
    return mSQLTypes;
    public StructureDef getStructureDef()
    return mStructureDef;
    public String getColumnType()
    return "NONAME";
    public String getString1()
    return (String)getAttribute(0);
    public void setString1(String value)
    setAttribute(0, value);
    public String getString2()
    return (String)getAttribute(1);
    public void setString2(String value)
    setAttribute(1, value);
    public Boolean getBoolie()
    return (Boolean)getAttribute(2);
    public void setBoolie(Boolean value)
    setAttribute(2, value);
    public void initStructureDef()
    DomainAttributeDef[] attrs = new DomainAttributeDef[3];
    if (mStructureDef == null)
    attrs[0] = new DomainAttributeDef("String1", "STRING1", 0, java.lang.String.class, 12, "VARCHAR", -127, 255, false);
    attrs[1] = new DomainAttributeDef("String2", "STRING2", 1, java.lang.String.class, 12, "VARCHAR", -127, 255, false);
    attrs[2] = new DomainAttributeDef("Boolie", "BOOLIE", 2, java.lang.Boolean.class, 2, "NUMERIC", -127, 0, false);
    mStructureDef = new DomainStructureDef(attrs);
    public CustomDatumFactory[] getAttrCustomDatumFactories()
    if (mCustDatFac == null)
    mCustDatFac = new CustomDatumFactory[3];
    mCustDatFac[0] = null;
    mCustDatFac[1] = null;
    mCustDatFac[2] = null;
    return mCustDatFac;
    And the XML file:
    <?xml version="1.0" encoding='windows-1252'?>
    <!DOCTYPE Domain SYSTEM "jbo_03_01.dtd">
    <Domain
    Name="ObjectTypeDomain"
    TimeStamp="1035407592087" >
    <DesignTime>
    <Attr Name="_isCodegen" Value="true" />
    <Attr Name="_version" Value="9.0.3.9.62" />
    <Attr Name="_type" Value="Struct" />
    <Attr Name="_columnType" Value="NONAME" />
    <Attr Name="_isUpdateable" Value="true" />
    <Attr Name="_isQueriable" Value="true" />
    <Attr Name="_isPersistent" Value="true" />
    <Attr Name="_isUnique" Value="false" />
    <Attr Name="_isNotNull" Value="false" />
    <Attr Name="_primaryKey" Value="false" />
    <Attr Name="_RetrievedOnUpdate" Value="false" />
    <Attr Name="_RetrievedOnInsert" Value="false" />
    <Attr Name="_DiscrColumn" Value="false" />
    </DesignTime>
    <Attribute
    Name="String1"
    Precision="255"
    Type="java.lang.String"
    ColumnName="STRING1"
    ColumnType="VARCHAR2"
    SQLType="VARCHAR" >
    <DesignTime>
    <Attr Name="_DisplaySize" Value="0" />
    </DesignTime>
    </Attribute>
    <Attribute
    Name="String2"
    Precision="255"
    Type="java.lang.String"
    ColumnName="STRING2"
    ColumnType="VARCHAR2"
    SQLType="VARCHAR" >
    <DesignTime>
    <Attr Name="_DisplaySize" Value="0" />
    </DesignTime>
    </Attribute>
    <Attribute
    Name="Boolie"
    Type="java.lang.Boolean"
    ColumnName="BOOLIE"
    ColumnType="NUMBER"
    SQLType="BIT" >
    <DesignTime>
    <Attr Name="_DisplaySize" Value="0" />
    </DesignTime>
    </Attribute>
    </Domain>

  • Issue Using Boolean Attribute in Decision Tables Conditions

    I'm using Oracle BPM Suite 11g 11.1.1.4.0 for my application. In my business rules, I need to use the nillable boolean attribute in Decision Table conditions, so I import java.lang.Boolean class in the Java Facts, I append .booleanValue() to the condition. I validate the rule, it's ok. Then I deploy my application to server, when I test the my process, i encounter a error:
    <bpelFault><faultType>0</faultType><operationErroredFault xmlns="http://xmlns.oracle.com/LoanApprovalRules/LoanApprovalRules_DecisionService_1"><part name="payload"><errorInfo xmlns="http://xmlns.oracle.com/LoanApprovalRules/LoanApprovalRules_DecisionService_1"><errorMessage>The class 'com.oracle.xmlns.bpm.bpmobject.data.loaninfoobject.LoanInfoObjectType' has no member named 'hasAssets'. at line 6 column 3 in main</errorMessage></errorInfo></part></operationErroredFault></bpelFault>
    HasAssets is Bool type. If I remove java.lang.Boolean in Java Fact, and remove conditions of hasAssets, the process run perfectly.
    Can you help me?
    Thanks.

    I'm using Oracle BPM Suite 11g 11.1.1.4.0 for my application. In my business rules, I need to use the nillable boolean attribute in Decision Table conditions, so I import java.lang.Boolean class in the Java Facts, I append .booleanValue() to the condition. I validate the rule, it's ok. Then I deploy my application to server, when I test the my process, i encounter a error:
    <bpelFault><faultType>0</faultType><operationErroredFault xmlns="http://xmlns.oracle.com/LoanApprovalRules/LoanApprovalRules_DecisionService_1"><part name="payload"><errorInfo xmlns="http://xmlns.oracle.com/LoanApprovalRules/LoanApprovalRules_DecisionService_1"><errorMessage>The class 'com.oracle.xmlns.bpm.bpmobject.data.loaninfoobject.LoanInfoObjectType' has no member named 'hasAssets'. at line 6 column 3 in main</errorMessage></errorInfo></part></operationErroredFault></bpelFault>
    HasAssets is Bool type. If I remove java.lang.Boolean in Java Fact, and remove conditions of hasAssets, the process run perfectly.
    Can you help me?
    Thanks.

  • JSPs using Custom Tag with Boolean attribute cannot compile

    Hi,
    In Oracle9iAS(9.0.3), a jsp using a tag extension, which has a Boolean attribute, caused the following compile error, although the jsp is valid in other web containers.
    ERROR:
    /opt/oracle/j2ee/home/application-deployments/simple/simple/persistence/_pages/_test.java:56: Method toBoolean(java.lang.Boolean) not found in class _test.
    __jsp_taghandler_1.setExists( OracleJspRuntime.toBooleanObject( toBoolean( b)));
    JSP:
    <%@ page language="java" %>
    <%@ page errorPage="error.jsp" %>
    <%@ taglib prefix="jnpr" uri="/WEB-INF/testtag.tld" %>
    <%
    Boolean b = Boolean.valueOf("true");
    %>
    <jnpr:TestTag exists="<%= b%>"/>
    The boolean value is <%= b %>
    Tag Handler:
    package defaultpak;
    import javax.servlet.jsp.tagext.*;
    import javax.servlet.jsp.*;
    public class TestTag extends TagSupport{
    private Boolean exists = null;
    private java.lang.Boolean getExists() {
    return exists;
    public void setExists(java.lang.Boolean newExists) {
    exists = newExists;
    public int doStartTag() throws JspException {
    return super.doStartTag();
    Is this a known problem? Is there a way to get around this?
    Thanks in advance.
    Fred

    This is a known issue with 903, fixed in coming 904.
    In 903 the workaround is to use primitive type "boolean" instead of Object type "java.lang.Boolean" in user's getter and setter code for the taglib.
    -Prasad

  • Custom Tag with boolean Attribute problems

    Hi,
    I've created a simple custom tag that is expecting a boolean attribute called "disabled". In my Tag derived class I've created a setDisabled(boolean b) method and set the following in the tag descriptor:
    <attribute>
         <name>disabled</name>
         <required>false</required>
         <rtexprvalue>true</rtexprvalue>
    </attribute>I'm using a JSTL expression "${someExpression}" which, when I do a c:out on the value, returns true.
    I call the tag like this:
    <mytag disabled="${someExpression}"/>However, in my custom tag class the value is passed as false. I can get true passed in if I hard code it, but that isn't going to work.
    I've tried a number of different combinations and even read through this forum for the last 2 hours and cannot seem to figure it out.
    What am I doing wrong?
    Thanks,
    John

    TLD File, per your previous recommendation:
    <attribute>
         <name>disabled</name>
         <required>false</required>
         <rtexprvalue>true</rtexprvalue>
         <type>boolean</type>
    </attribute>My Tag class (snippet):
    public class ButtonTag extends TagSupport
      private boolean disabled;
      public ButtonTag() {}
      public boolean isDisabled()
         return disabled;
      public void setDisabled(boolean b)
        disabled = b;
    }A sample of the jsp file invoking it:
    <c:set var="result" value="${computedValue}"/>
    <ltm:button disabled="${result}"/>Regardless of the value of result, ("true" or "false") it always passes false to the setDisabled method of the button tag class.

  • How to set default value in transient boolean attribute in VO in ADF

    Hi ADF Experts,
    I have requirement like,I have viewObject with one transient booelan attribute,
    I want to set default value of that boolean attribute as "True"
    How can I achive that please help,
    Tried every thing but no luck.

    Hi,
    I am not sure what is the use of setting a default value for a transient attribute in a read-only VO.
    However, why not include that attribute with a default value in the query itself?
    Something like
    SELECT
         Empno, Ename, Deptno, 'true' as BooleanTransAttr
    FROM EMP
    and set the type of the attribute to Boolean?
    -Arun

  • Updating custom boolean attribute in Active Directory via OIM

    The adapters delivered with the AD connector support updating standard attributes (string) and multi-value attributes, but I can't seem to figure out how to update a custom Boolean attribute in AD via OIM. The delivered Boolean fields all appear to have custom adapters (ie Account Locked, Password Never Expires, etc.)
    I've tried using the delievered adpADCSCHANGEATTRIBUTE adapter, but it fails (as expected) with:
    +com.thortech.xl.integration.ActiveDirectory.tcUtilADTasks : updateDetails : Attributes cannot update:[LDAP: error code 21 - 00000057: LdapErr: DSID-0C090B73, comment: Error in attribute conversion operation, data 0, v1772 ]+
    Suggestions?

    No I don't have custom boolean attributes in AD. But I added custom attributes of other types.
    When you say custom, do you mean it did not come with the out of the box AD connector, but exists in the Active Directory of your organization?
    There are a few attributes in AD which look like they are boolean when you see the AD console but are actually different. Look at the link for details.
    [http://support.microsoft.com/kb/305144]
    Look at this post for context.
    AD Provisioning - Password never expires & User must chg pwd at next logon
    Thanks,
    M

  • Boolean attributes and SQL column types

    I have a MS SQL database table I am managing with SIM. One of the attributes needs to represent a boolean value. In my schema, the attribute is:
    <AccountAttributeType id='17' syntax='boolean'
                          name='foreignStudent' mapName='Foreign_Student'
                          mapType='string'/>which is what is generated when editing the Resource Schema through the administrative UI.
    What data type should I be using for the column in SQL? I have tried bit, tiny int and char(1), but am always seeing the same issue. When I save the user, the accounts[...].foreignStudent is true, and SIM sets the value in the database column to 1 (or '1'). But when I open the user again, accounts[...].foreignStudent is read in as false, and so SIM thinks it needs to update the resource.
    Same thing happens if I try a mapType='boolean' or mapType='integer'.
    Thanks in advance!

    Thanks, Paul, but although I have some flexibility in the database design, I need the column to hold either a 0/1 or F/T.
    I have worked around it by treating it as an int and not a Boolean, and making sure I just assign values of 0, 1 and null. But I am curious to know if anyone has successfully mapped a boolean attribute type to a SQL bit type rather than varchar(5)...

  • Pros and Cons - Representation of boolean attributes

    A coworker and I are discussing the different ways to represent boolean attributes in a new schema.
    So far, there are three options we came up with and were wondering what the pros, cons, and opinions were. There are many attributes that work like the following examples:
    Addresses - A person may have multiple addresses
    Shipping Address - One and only one address is the shipping address for a person
    1) shipping is a boolean attrbiute of the Addresses table represented by a char(3) datatype than can be "yes" and "no"
    2) A seperate shipping address table contains a primary key made up of the primary key from the People table and the primary key from the Addresses table.
    3) One intermediate table is made for all the boolean value associated with the address entity, creating a many to many relationship between Addresses and "boolean attributes".
    I prefer 1, he prefers 2 and suggested 3.
    I like 1, because
    It enforces the relationship that a person can only have one shipping address, since the key is composed of a person and an address, and is unique.
    It is also easy to add too or drop when clients change their minds as much as they do. I can also associate extra data with it if the users decide to start asking for more (they often do)
    I dislike 2, because I have to actually compare text to get a boolean value. It also leaves room for people to make typos or put something besides yes or no. I don't mind 2 of an entity happens to have bunches of boolean attributes as I don't want to create 25 seperate tables...I guees it depends on what the data is.
    We've got attributes that work like this all over the place. Shipping addresses, billing addresses, primary phone number, primary email address. Courses that are 'advanced" courses, active vs non active, etc.
    I see his argument for long queries or too many tables, if an entity has many boolean attributes and I start making tables for all of them, but when there are 1-4 I think it makes more sense to make a seperate table for groupings of things. I see it more as a subset than an attribute...Give me all the addresses that are shipping addresses or give me all the courses that are not in the active course table.
    What are your thoughts?
    Edited by: brekehan on Apr 16, 2010 11:12 AM

    user12999515 wrote:
    This is the coworker trying to clarify the question. There is a distinct possibility that an entity represented in a database may have Boolean attributes. So the question is what is the best way to represent them. The first answer is to make them a column of a table. But let's think about it. What if we are going to search by these attributes.
    A solution is to have a separate table for each Boolean attribute pointing to the primary key of the addresses table. In this case shipping address and billing address.Sure you could do that, but then you introduce a few complexities, and i'm not sure i see where the tangible benefit is. With the example provided by your colleague you would have.
    Entity = address (pk_value, <other_columns>)
         where pk_value = person_id, some incremented ID for address
    Entity = shipping address (pk_value)
         where pk_value = person_idSo this takes care of the business rule that a person can have at most 1 shipping address (that's good), but when you want to know ALL the address information for a given person on file you need to query
    select
       a.*,
       case when sa.person_id is null then 'NO' else 'YES' end as shipping_address
    from addresses a, shipping_address sa
    where a.person_id = :person_id
    and a.person_id = sa.person_id (+)As opposed to
    Entity = address (pk_value, shipping_address, <other_columns>)
         where pk_value = person_id, some incremented ID for address
         shipping_address = 0 or 1
         with a check constraint on shipping_address ( in (0,1) )
         with a unique index to enforce the rule that a person can have at most one shipping address .. which would look something like
    drop table addresses;
    create table addresses
         person_id number,
         address_id number,
         shipping_address     number(1),
         constraint addresses_pk primary key (person_id, address_id),
         constraint addresses_c1 check (shipping_address in (0,1))
    create unique index addresses_u01 on addresses (case when shipping_address = 1 then person_id else null end);
    --shows the unique index enforcing the business rule that 1person can have at most 1 shipping address
    insert into addresses values (1, 1, 0);
    insert into addresses values (1, 2, 0);
    insert into addresses values (1, 3, 1);
    --take a break, add someone else's info
    insert into addresses values (2, 2, 0);
    insert into addresses values (2, 3, 1);
    --back to person 1, add another shipping address (which will raise an error because of our index)
    insert into addresses values (1, 4, 1);And when querying this table we have a simple
    select
       a.*
    from addresses a
    where a.person_id = :person_id
    --if you need to, decode(shipping_address, 0, 'NO', 'YES')When you start getting into adding tables to represent a 1 – 1 relationship, you're really adding overhead. In this case, instead of adding a single column (with a number(1) datatype) you'll be adding a table with a number(x) where x is the length of your person_id. So the storage goes up (i won't argue this is a big deal as we're in the year 2010 :) however when you need to query you now have 2 tables to grab data from which means more IO (you have data blocks for the address table, and data blocks for the shipping_address table).
    Unless you have a situation like the following
    http://www.oracle.com/technology/oramag/oracle/09-mar/o29asktom.html “Wide Load Storage” i would recommend staying away from modelling 1 – 1 relationships.

  • Custom search using boolean attribute set to True gives no result

    I am setting up an auto-query using the custom search portlet. This is to show all items where a boolean custom attribute is checked, ie = True.
    In step 3 I have tried to set the operator to Equals to and the default value to True. This gives no results even though several items have this attribute set to True.
    The Auto Query check box is checked.

    Found that True = 1 in database. When set to this the search works.

  • Bug: unable to rename entity attribute (jdev903)

    Hi,
    I have an entity and a view on it.
    One of the entity attributes has the wrong name, so I tried to rename it, but jdev gave me a warning that it couldn't rename the attribute because the view is dependent on it. Sounds fair (although I wish it would rename the attribute in the view along with it, (refactoring)).
    Then I removed the attribute from the view, and try to rename the entity attribute again. It still can't rename it! I've verified twice to see if the attribute was actually removed from the view, which it was, so this is definitely a bug.
    Greetings,
    Ivo

    Ivo want's to rename the attribute in the entity object without first removing the attribute from the view object. That this isn't possible right now probably isn't a bug, because in your scenario you keep that in mind, so you manually first remove the attribute from the view object. But it would be nice if JDeveloper automatically renames the attribute in the view object too (instead of "complaining" about the dependency). And if you for example remove an attribute from an entity and a view object depends on it, it will ask you to remove the attribute from the view object(s) too etc.

  • [Help plz]Can't set a boolean attribute to true or false

    Hello,
    I'm new in NWDS development. I need to develop a download functionality
    I used a FileDownload UIElement for that and I created a node context (ExcelExport) with 3 attributes :
    - ExcelFile
    - ExcelIcon
    - And ExcelEnabled (Boolean type)
    My problem is that everytime I try to set the attribute ExcelEnabled to true or false, it return me a java.lang.NullPointerException
    I'm binding this attribute with "Enabled" property of the UIElement.
    Have anyone got this error before? Thanks a lot for your help.
    Kind regards,
    Safae.

    Hello Safae,
    Have you tried to put true/false value for the enabled property? I mean without using a context attribute?
    Also try to create the attribute out of the node.
    Regards,
    ImaneA.

  • 10g Preview: BUG: Infinite loop renaming entity attribute

    9.0.5.0.0, Build 1375, Win2k SP3.
    BACKGROUND:
    After attempting to rename an EO on which a VO was based I received an error that indicated the VO was dependent on the attribute to be renamed. I removed the VO attribute from the VO's attribute list and saved the changes. I then brought up the Entity Object wizard where I attempted to rename the attribute.
    When jdevw.exe is used to launch the IDE, the renaming action results in the IDE hanging. When jdev.exe is used, the console prints the following stack trace and the IDE gives a StackOverflowError.
    java.lang.StackOverflowError
         at java.lang.System.arraycopy(Native Method)
         at java.lang.StringBuffer.expandCapacity(StringBuffer.java:203)
         at java.lang.StringBuffer.append(StringBuffer.java:393)
         at oracle.jbo.dt.objects.JboBaseObject.getFullName(JboBaseObject.java:188)
         at oracle.jbo.dt.objects.JboEntity.attributeChangeQuery(JboEntity.java)
         at oracle.jbo.dt.objects.JboChangeMulticaster.dispatchAttributeRemoveQuery(JboBaseObject.java)
         at oracle.jbo.dt.objects.JboEntity.attributeChangeQuery(JboEntity.java)
    [...a few hundred thousand more of these...]
         at oracle.jbo.dt.objects.JboChangeMulticaster.dispatchAttributeRemoveQuery(JboBaseObject.java)
         at oracle.jbo.dt.objects.JboEntity.attributeChangeQuery(JboEntity.java)
         at oracle.jbo.dt.objects.JboChangeMulticaster.dispatchAttributeRemoveQuery(JboBaseObject.java)
         at oracle.jbo.dt.objects.JboEntity.attributeChangeQuery(JboEntity.java:388)
         at oracle.jbo.dt.objects.JboChangeMulticaster.dispatchAttributeRemoveQuery(JboBaseObject.java:3394)
         at oracle.jbo.dt.objects.JboEntity.attributeChangeQuery(JboEntity.java:388)
    [...and a bunch of these...]
         at oracle.jbo.dt.objects.JboChangeMulticaster.dispatchAttributeRemoveQuery(JboBaseObject.java:3394)
         at oracle.jbo.dt.objects.JboEntity.attributeChangeQuery(JboEntity.java:388)
         at oracle.jbo.dt.objects.JboChangeMulticaster.dispatchAttributeChangeQuery(JboBaseObject.java:3427)
         at oracle.jbo.dt.objects.JboObject.changeAttributeQuery(JboObject.java:107)
         at oracle.jbo.dt.ui.entity.AttributeSettingsPanel.attributeNameCheck(AttributeSettingsPanel.java:453)
         at oracle.jbo.dt.ui.entity.EOAttributePanel.leave(EOAttributePanel.java:279)
         at oracle.jbo.dt.ui.entity.EOAttributeTabPanel.leave(EOAttributeTabPanel.java:108)
         at oracle.jbo.dt.ui.entity.EOEditAttributeTabPanel.updateCurrentAttr(EOEditAttributeTabPanel.java:330)
         at oracle.jbo.dt.ui.entity.EOEditAttributeTabPanel.leave(EOEditAttributeTabPanel.java:113)
         at oracle.jbo.dt.ui.main.dlg.DtjMddTraversable.onExit(DtuMddNavigable.java:278)
         at oracle.ide.panels.MDDPanel.exitTraversable(MDDPanel.java:761)
         at oracle.ide.panels.MDDPanel.onExit(MDDPanel.java:286)
         at oracle.jbo.dt.ui.main.dlg.DtjMddWizardDialog.okAction(DtuWizard.java:1899)
         at oracle.jbo.dt.ui.main.dlg.DtjDialog.dismissDialog(DtjDialog.java:219)
         at oracle.bali.ewt.dialog.JEWTDialog$UIListener.actionPerformed(Unknown Source)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1764)
         at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1817)
         at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:419)
         at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:257)
         at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:245)
         at java.awt.Component.processMouseEvent(Component.java:5134)
         at java.awt.Component.processEvent(Component.java:4931)
         at java.awt.Container.processEvent(Container.java:1566)
         at java.awt.Component.dispatchEventImpl(Component.java:3639)
         at java.awt.Container.dispatchEventImpl(Container.java:1623)
         at java.awt.Component.dispatchEvent(Component.java)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java)
         at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3165)
         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3095)
         at java.awt.Container.dispatchEventImpl(Container.java:1609)
         at java.awt.Window.dispatchEventImpl(Window.java)
         at java.awt.Component.dispatchEvent(Component.java)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:452)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:197)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:141)
         at java.awt.Dialog.show(Dialog.java:538)
         at java.awt.Component.show(Component.java:1134)
         at java.awt.Component.setVisible(Component.java:1089)
         at oracle.jbo.dt.ui.main.dlg.DtjDialog.setVisible(DtjDialog.java:137)
         at oracle.jbo.dt.ui.main.dlg.DtjMddWizardDialog.setVisible(DtuWizard.java:1926)
         at oracle.bali.ewt.dialog.JEWTDialog.runDialog(Unknown Source)
         at oracle.jbo.dt.ui.main.dlg.DtjDialog.showDialog(DtjDialog.java:114)
         at oracle.jbo.dt.ui.main.dlg.DtjMddWizardDialog.showDialog(DtuWizard.java:1885)
         at oracle.jbo.dt.ui.main.dlg.DtuWizard.createMddWizard(DtuWizard.java:422)
         at oracle.jbo.dt.ui.main.dlg.DtuWizard.setVisible(DtuWizard.java:276)
         at oracle.jbo.dt.ui.entity.EOWizard.setVisible(EOWizard.java:204)
         at oracle.jbo.dt.ui.main.dlg.DtuWizard.showDialog(DtuWizard.java:254)
         at oracle.jbo.dt.jdevx.ui.JdxMenuManager.invokeEOWizard(JdxMenuManager.java:762)
         at oracle.jbo.dt.jdevx.ui.JdxMenuManager.invokeEntityWizard(JdxMenuManager.java:741)
         at oracle.jbo.dt.ui.main.DtuMenuManager.doEditMenuAction(DtuMenuManager.java:1341)
         at oracle.jbo.dt.ui.main.DtuMenuManager.doMenuAction(DtuMenuManager.java:1218)
         at oracle.jbo.dt.jdevx.ui.JdxMenuManager.doMenuAction(JdxMenuManager.java:701)
         at oracle.jbo.dt.ui.main.DtuMenuManager.doAction(DtuMenuManager.java:1058)
         at oracle.jbo.dt.ui.main.DtuMenuManager.doAction(DtuMenuManager.java:1041)
         at oracle.jbo.dt.jdevx.ui.JdxMenuManager.doActionPerformed(JdxMenuManager.java:532)
         at oracle.jbo.dt.jdevx.ui.JdxMenuInvoker.run(JdxMenuManager.java:1285)
         at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:449)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:197)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:136)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:99)

    Thanks for the post, I've been able to reproduce this in the current builds and I've logged this as bug #3159091 to be fixed for 9.0.5 production.
    Ray

Maybe you are looking for

  • Advance & Retension for a vendor

    Dear Friends, My Issue: For a vendor my payment should be: --> 10% Advance of the total Contract should be given to the Vendor --> when ever vendor invoices (partial invoices) we should cut 10%(on advance given before) and 10% Retension and pay him 8

  • Problem with SSL socket(SSLSocketFactoryImpl.createSocket())

    Hello, I'm trying to create a ssl socket but I get an exception, I really don't know why. I have alredy include the certificate via keytool to my jdk. And I'm able to get html header with URLConnection with the code below import java.net.URL; import

  • 2nd email address on one account?

    looking for info on how to create a second email address for myself. I'd like to keep the existing one (my [email protected]) AND create another one for privacy ([email protected]). Where do I go to do this? Can I have incoming mails to both addresse

  • Exchange 2013 -Distribution Group

    Hi - Let me explain my issues here. I am the Part of DL called Itadmins in exchange server 2013. When ever I send a mail to itadmins I am getting copy of the mail back to me again. Is this expected behavior in exchange server 2013 ? Regards, Srinivas

  • IPOD mini click wheel not  functioning

    My IPOD mini click wheel is not working. When I attach to my PC, Itunes recognizes it, is able to read the hard drive/play music off the IPOD. I have tried to restore it, the drive is erased, but the click wheel still does not work. I am unable to re