BC4J bug in 9.0.3.3

Hi,
I've just downloaded Jdev 9.0.3.3 and the very first thing I tried seems to have a bug. I tried to remove an attribute from a BC4J entity using the Entity Object Editor. The first thing it does is lock up for about a minute, then it eventually starts responding again. However, the attribute I deleted still exists so I press the Delete button again - the IDE immediately crashes. Is this a bug -it certainly didn't do this in previous versions of Jdeveloper.
Steve

And they said:
Bug:3120608 DELETING AN ENTITY ATTRIBUTE CAUSES EXCEPTION, THEN CRASHES JDEV,
this bug is an internal one, filed for version 9.0.5.13.66 and fixed in version 9.0.5.13.67.
So don't hold your breath!
Sascha

Similar Messages

BC4J bug with "bind variables" JBO-27122 ORA-01008

I think we are found a BUG using BC4J with bind variables in a view object.
If the bind variable appear in the WHERE condition two or more times at
the beginning of the query the above error occur.
oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation. Statement:
SELECT Emp.EMPNO,Emp.ENAME,Emp.JOB,Emp.MGR,Emp.HIREDATE,Emp.SAL,Emp.COMM, Emp.DEPTNO
FROM SCOTT.EMP Emp
WHERE :1 <=10000 and :1 <= sal and :2=20
java.sql.SQLException: ORA-01008: not all variables bound
Otherwise if bind variable apper two or more times, but not together
like this sample:
WHERE :1 <=10000 and :2=20 and :1 <= sal
the error not occur.
We prove this with:
JDeveloper 9.0.5.2 (build 1618)Business Components Version 9.0.5.16.0
JDeveloper 9.0.5.0 (build 1375)Business Components Version 9.0.5.13.52
I looking for a patch! or acceptable workaround.
Tx for your help!
diego.
/* the cliente app */
ApplicationModule am = Configuration.createRootApplicationModule("business_tier.AppModule","AppModuleLocal");
ViewObject vo = am.findViewObject("EmpView");
vo.setWhereClauseParam(0,"100");
vo.setWhereClauseParam(1,"20");
Row emp = vo.first();

This is a known bug (1326006). The workaround is to use:
vo.setWhereClauseParam(0,"100");
vo.setWhereClauseParam(1,"20");
vo.setWhereClauseParam(2,"20");
Hope this helps,
Lynn
Java Tools Team

Bc4j bug at refresh after insert / update

having a table and a trigger on it that fills an attribute
in a 9i db. one can take the scott/tiger emp table and use the
following trigger:
create or replace trigger t_bri_emp
before insert on emp
for each row
declare
v_no number(7,2);
begin
select user_SEQ.nextval*100
into v_no
     from dual;
:new.sal := v_no;
end;
then creating a bc4j project with an entity object based on this table (emp)
and a view object based on the created entity object.
!!!! when you create the bc4j project you must set the SQL Flavor to SQL92 or OLite
when you set the attribute settings, for the attribute the trigger is on (sal),
to refresh after insert / update or both in the entity object you get a
null pointer when you try to insert a new row and commit.
java.lang.NullPointerException
     oracle.jdbc.ttc7.TTIoac oracle.jdbc.ttc7.TTCAdapter.newTTCType(oracle.jdbc.dbaccess.DBType)
     oracle.jdbc.ttc7.NonPlsqlTTCColumn[] oracle ....................
all can be reproduced just useing the wizard and start the bc4j project with the tester
any workaround ??

Sven:
I looked into your issue. It turns out your problem is caused by a bug in the system (bug #2409955).
The bug is that for non-Oracle SQLBuilder, we are not processing refresh-on-insert and refresh-on-update attributes correctly. We end up forming an invalid SQL statement and the JDBC driver gives the obscure NullPointerException.
Thus, until 9.0.3, you should not use refresh-on-insert/update attributes on a non-Oracle SQLBuilder.
If you need the refresh-on-insert/update attribute, here is a possible workaround:
1. Whenever you invoke the tester, on the first panel, click on the 'Properities' tab. In the list of properties, you should find one for 'jbo.SQLBuilder'. It will say 'SQL92'. Remove it, so that it is empty. Run test tester. Then, the tester will use Oracle SQLBuilder which will handle refresh-on-insert/update attributes correctly for you.
2. For switching between Oracle SQLBuilder and SQL92 SQLBuilder, you can try the following:
2a) Locate bc4j.xcfg and your Project??.jpx under your 'src' directory.
2b) Make copies of these files.
2c) Edit them so that you have one set for Oracle SQLBuilder and one set for SQL92 SQLBuilder. For Oracle SQLBuilder, make sure these files do NOT have entries like:
<jbo.SQLBuilder>..</jbo.SQLBuilder> in bc4j.xcfg and
<Attr Name="_jbo.SQLBuilder" Value="..." /> in Project??.jpx
When there is no jbo.SQLBuilder entry, BC4J will default to Oracle.
For SQL92, make sure you have
<jbo.SQLBuilder>SQL92</jbo.SQLBuilder> in bc4j.xcfg and
<Attr Name="_jbo.SQLBuilder" Value="SQL92" /> in Project??.jpx.
Before you run, decide which SQLBuilder to use (for 9.0.2, with retrieve-on-insert/update attrs, you have no choice but to use Oracle SQLBuilder) and copy these files into your class path, e.g.,
<jdev-install-dir>\jdev\mywork\Workspace1\Project1\classes
When you get 9.0.3, then you should be able to switch between Oracle and SQL92 SQLBuilders freely.
Thanks.
Sung

UIX XML-BC4J: Bug on messageTextInput

We have found a bug on the BC4J:messageTextInput tag because it doesn't use the value of "prompt" attribute to generate client validating messages.
Message alerts displayed on browser are on the following form:
Form Validation failures: a value must be entered for ''
PS: this problem did not occur with BC4J:messageInput but we can't use it because it doesn't support the onSubmitValidater inner tag to specify the field type.

Try explicitly setting the "id" to a unique value; that should fix the problem.
It is a bug, but one that won't be fixed for 9.0.3.

UIX/XML BC4J Bug on "selectedValue" attribute

We suspect a bug in tag bc4j:attrProperty when used within boundAttribute because bounding
it to property selectedIndex works correctly, while bounding it to selectedValue result in a
Servlet error: Renderer failed: java.lang.ArrayIndexOutOfBoundsException
Correctly executed code (but logically wrong):
<bc4j:attrScope name="FlgObsoleto">
<contents>
     <messageChoice name="FlgObsoleto" prompt="Stato">
          <boundAttribute name="selectedIndex">
               <bc4j:attrProperty name="value"/>
          </boundAttribute>
          <contents>
               <option value="2" text="Element 0"/>
               <option value="0" text="Element 1"/>
               <option value="34" text="Element 2"/>
          </contents>
     </messageChoice>
</contents>
</bc4j:attrScope>
Code resulting in error (but logically correct):
<bc4j:attrScope name="FlgObsoleto">
<contents>
     <messageChoice name="FlgObsoleto" prompt="Stato" >
          <boundAttribute name="selectedValue">
               <bc4j:attrProperty name="value"/>
          </boundAttribute>
          <contents>
               <option value="2" text="Element 0"/>
               <option value="0" text="Element 1"/>
               <option value="34" text="Element 2"/>
          </contents>
     </messageChoice>
</contents>
</bc4j:attrScope>

The infamous ArrayIndexOutOfBoundsException - argh. This always means
some other, real exception has happened. In this case, it's a
ClassCastException as some bad code of ours blindly casted to
String. This is fixed in 9.0.3. In 9.0.2, there's a clumsy
workaround to force the attribute type to a string and dodge the bug.
Change this one instance of:
<bc4j:attrProperty name="value"/> to:
<concat>
<bc4j:attrProperty name="value"/>
<fixed text=""/>
</concat>Ugly. Very, very ugly!

BC4J: bug query generator

Hi,
We want to use a certain name for a table in our database. Unfortunately this name is protected. To circumvent this problem we created the table with the name between quotes (e.g. "table"). This works fine at the database level.
If we add the table to a BC4J package using JDeveloper an entity with the right name (e.g. Table) is created. Unfortunately this name is used by default as a synonym to query the table (e.g. SELECT * FROM "table" Table). Fortunately for normal select statements you can change this by editing the view object and renaming the default synonym to something else (e.g. SELECT * FROM "table" t).
But... when you try to remove a row BC4J still uses the default synonym to first lock the record and then delete the record. Unfortunately there seems to be no way to change the default table synonym of a certain entity. Or is there a way?
Regards,
Peter

I've found a way to circumvent the problem. Although normally it's not possible (in the JDeveloper GUI) to enter an alias for a certain entity, it is possible when you edit it's XML file. If you change the attribute AliasName to a valid alias everything works fine!

[BC4J-bug] obsolete import statements remain behind in AM source file

Just wondering if the following problem is a known bug or not:
I've got an application module called 'AMExample' and it consists of 2 files: AMExample.xml and AMExampleImpl.java.
When I remove a view from this module, the corresponding import statement in the AMExampleImpl.java file remains behind, which leads to compilation errors after I delete this (obsolete) view entity from the project.
Regards,
Patrick.

Just wondering if the following problem is a known bug or not:
I've got an application module called 'AMExample' and it consists of 2 files: AMExample.xml and AMExampleImpl.java.
When I remove a view from this module, the corresponding import statement in the AMExampleImpl.java file remains behind, which leads to compilation errors after I delete this (obsolete) view entity from the project.
Regards,
Patrick.

BC4J BUG:Attribute Property Editor:Lost properties

I've been the victim numerous times of this bug. Just able to figure it out and articulate it:
When editing an Attribute, go to the "Properties" page and enter multiple properties (i.e. Renderer, EditRenderer, etc.). Don't save your changes and go to another page (i.e. "Control Hints"). Make a change (or not-didn't test it) and don't save your changes. Then go back to the "Properties" page. All the properties you had entered except the last will be gone and that last property will not be shuttled.
Work around:
Hit "Apply" before going back to the "Properties" page.
Don't re-enter the "Properties" page.
Hit "Ok" and then re-open the Attribute Wizard before going back to the "Properties" page.
Thanks, George

I've been the victim numerous times of this bug. Just able to figure it out and articulate it:
When editing an Attribute, go to the "Properties" page and enter multiple properties (i.e. Renderer, EditRenderer, etc.). Don't save your changes and go to another page (i.e. "Control Hints"). Make a change (or not-didn't test it) and don't save your changes. Then go back to the "Properties" page. All the properties you had entered except the last will be gone and that last property will not be shuttled.I believe you've already logged this post earlier. Incase you haven't seen the reply,
There's an Add button on the "Properties page" which you need to click after editing/providing a new property/value pair. Then you should see the property/value in the list below the add/remove buttons
For each property value pair you should repeat these steps for the property/value pair to be stored.
Work around:
Hit "Apply" before going back to the "Properties" page.
Don't re-enter the "Properties" page.
Hit "Ok" and then re-open the Attribute Wizard before going back to the "Properties" page.
Thanks, George

10g BC4J bug in alias query column

something strange ... i created some view's in expert mode and gave the result set aliases to replace the expression used in the select clause (select expression "Alias" from ...). The alias was mixedcase like in the parenthesis. After creating two view's i created a view link using both attributes (transient attributes resulting from the expression). All seem to were fine but i have got an error when testing the application module where the view's was integrated. The error said that the "Alias" was not recognize. Changing the alias to "ALIAS" (in uppercase) resolved the problem.

Forgot to mention why this is a problem:
If I can't change the alias, the queries look 'confusing', because the default alias is the name of the base entity. So the query becomes:
SELECT ...
FROM Derived BASE
This is confusing.

10g BC4J bug

It is not possible to remove a transient attributes in a view created with expert mode. although the wizard remove the attribute from the list box using the left arrow button the attributes still in the view and come back after appying the changes (apply button).

Sorted. You have to execute jdevw.exe not jdex.exe
My mistake.

BC4J+UIX:Is it a bug?

There is a strange problem:
I use a null event to init a vo,as following:
<?xml version="1.0" encoding="GBK"?>
<page xmlns="http://xmlns.oracle.com/uix/controller"
xmlns:ui="http://xmlns.oracle.com/uix/ui"
xmlns:ctrl="http://xmlns.oracle.com/uix/controller"
xmlns:html="http://www.w3.org/TR/REC-html40"
xmlns:bc4j="http://xmlns.oracle.com/uix/bc4j">
<bc4j:registryDef>
<bc4j:rootAppModuleDef name="VTbReceiveListView1AppModule"
definition="Project.PropakModule"
releaseMode="stateful">
<bc4j:viewObjectDef name="VTbReceiveListView1" rangeSize="20" />
</bc4j:rootAppModuleDef>
</bc4j:registryDef>
<content>
<event name="null">
<bc4j:findRootAppModule name="VTbReceiveListView1AppModule">
<method class="propackage.ReceiveListAffirm" method="initReceiveList"/>
</bc4j:findRootAppModule>
</event>
and the event is :
public static EventResult initReceiveList(
BajaContext context,
Page page,
PageEvent event) throws Throwable
String sWhere="";
double dAmountGross=0,dAmountVat=0,dAmount=0;
ApplicationModule amThis = ServletBindingUtils.getApplicationModule(context);
HttpSession session = context.getServletRequest().getSession(true);
sWhere = "VALIDATED_MARK = 'N' AND "+ session.getAttribute("GuoSessionWhere").toString();
voThis.setWhereClause(sWhere);
voThis.executeQuery();
int length = voThis.getFetchedRowCount();
EventResult result = new EventResult(page);
return result;
the value of length is 0 when i first run the page.
However,when i refresh(F5) this page,it is 9(the right number).
Who can tell me the reason?

This post is the same as the post on the JDeveloper forum at:
UIX+BC4J BUG: Is it a bug?
Please keep all followups to the other thread.
-brian
Team UIX
PS: Please do not post the same question to the JDev and UIX forums, as they are monitored by the same people.

UIX/BC4J: messageTextInput nulls out data.

I switched a page from the use of messageInput to messageTextInput. This was so I would be able to control the attributes of the field better. However, now when I select Update instead of saving the new data it deletes it from the database. messageInput works messageTextInput nulls the data in the database.
I tried setting the id value according to the note "UIX XML-BC4J: Bug on messageTextInput" but this did not solve my problem.
Here is an example of one of the fields I changed:

<bc4j:messageTextInput id="genNotes"
attrName="NOTES_GEN"
prompt="Notes"
columns="75"
rows="4"
maximumLength="1000"
wrap="hard"/>
Any ideas?

We aren't properly defaulting the "name" attribute
of <bc4j:messageTextInput> in the same way that we
default it for <bc4j:messageInput>.
So, set the "name" to match "attrName":
<bc4j:messageTextInput id="genNotes"
attrName="NOTES_GEN"
name="NOTES_GEN"
etc...
/>
This has been fixed since 9.0.3 (the "name" problem,
but unfortunately not the "id" problem).

Detail Group Problem

Hello All,
I have a DB that uses intermediate tables a lot. An intermediate table is one that breaks up a many-to-many relationship between two tables; by putting a table between them that uses the primary keys from both tables.
E.g. EMPLOYEE and PROJECT tables: Many Employees work on One Project; or One Employee works on Many Projects.
Here's the JHeadstart problem (9.0.4, Struts/UIX): Using the XML Application Editor, I created a Group called EMPLOYEE (select-form) and added some Lookups to it. I then added a Detail Group called EMPLOYEE_PROJECT and set it up as a table on a separate page. The application compiles without errors, but when I bring up the application and click on the "Employee-Project" tab, I receive the following error:
JBO-27122: SQL Error. "Select EMPPROJ.empid, EMPPROJ.projid, FROM EMPLOYEE_PROJECT empproj WHERE (EMPPROJ.empid =: 1) ORDER BY EMPPROJ.empid, EMPPROJ.projid"
The error comes from the WHERE clause, specifically the "=:1" part. SQL Worksheet calls the error a bad bind variable when I run the query in it. What's funny, is that the Master Detail page had Employee Number 5 up; so the query should have had the employee ID of 5, not 1. No matter which employee I bring up on the master view, I still get the same WHERE clause with the "=:1" error.
I tried adding other intermediate tables to the Master Employee detail group and get the same results.
Anyone see this before?
I suspect there's a JHeadstart setting somewhere related to the Master Detail, but I'm stumpred as to what it is.
Any thoughts or opinions would be appreciated.

Tracy-Paul,
Are you using JDeveloper 9.0.3.3 or 9.0.3.4?
If so, you are probably running into BC4J bug 3214032. In the JHeadstart 9.0.4.5 release notes the following info is included:
3214032: JBO-27122: SQL error during statement preparation and ORA-1722 INVALID NUMBER IF PARENT VO ROW IN VIEW LINK REORDERS ATTRS. This bug can occur if you are using the BC4J libraries of JDeveloper 9.0.3.3 or 9.0.4.0 (or 9.0.5 Preview) and in one of your View Objects the Primary Key attribute(s) have a different index number than the Primary Key attribute(s) in the corresponding Entity Object. For example: in the Entity Object the primary key is the first attribute, but in the View Object the primary key is the last attribute. If this occurs, a workaround is to change the order of the View Object attributes.
So, you can try to reorder your attributes, or to use the BC4J libraries of JDeveloper 9.0.3.2.
We have been in close contact with BC4J product development about this bug, and they promised to publish a one-off patch for this bug on metalink as soon as possible. So keep your eye on metalink, you can also read the bug report there.
Steven Davelaar,
JHeadstart Team.

SetAttribute() doesn't affect transaction state

I have BC4J JSP application and I have problem with one my ViewObject, it is very similar as the other my ViewObjects, is it based on one Entity and it is on third level master-detail (master-detail1-myVOdetail2).
But its behavior is very strange.
1) I call setAttribute("attrName"), no matter which attribute it is. (getAttribute() returns a new value).
2) I call Transaction.isDirty() -> false returned!!!!
3) I make some change, setAttribute() on the other ViewObject.
4) I call Transaction.isDirty() -> true returned.
5) I call commit() -> both changes made by points 1. and 3. are posted and commited to database.
It is very strange - may be some bc4j bug? Or some my mistake. I never have meet this problem before...
Have you any idea, what's the problem?
The problem is normally repeatable. My JDev version is 9.0.4.
Thank you very much for any comment.
Jan

repost

9.0.3.3: NPE in ViewDefImpl

We're testing 9.0.3.3 right now.
When we create a new row:
public void addToAssigned( Row[] rows ) {
    //passed rows must come from availableVO, otherwise that won't work correctly
    BaseViewObject availableVO = (BaseViewObject)binding.getApplicationModule( )
                                                            .findViewObject( availableView );
    BaseViewObject assignedVO = (BaseViewObject)binding.getApplicationModule( )
                                                           .findViewObject( assignedView );
    AttributeDef keyAvailableAttributeDef = availableVO.findAttributeDef( keyAvailableAttributeName );
    for( int i = 0; i < rows.length; i++ ) {
      String keyName = keyAvailableAttributeDef.getName( );
      Object value = rows[ i ].getAttribute( keyName );
      Row row = assignedVO.createRow( );
      row.setAttribute( keyAssignedAttributeName, value );
      assignedVO.insertRow( row );
    binding.getApplicationModule( ).getTransaction( ).postChanges( );
    assignedVO.executeQuery( );
}This causes a:
2003-10-23 17:37:12,315 [AWT-EventQueue-0] ERROR com.ge.med.bone.exception -
java.lang.NullPointerException
     at oracle.jbo.server.ViewDefImpl.processEntityAssociations(ViewDefImpl.java:3268)
     at oracle.jbo.server.ViewAttributeDefImpl.getEntityAssociationReferences(ViewAttributeDefImpl.java:566)
     at oracle.jbo.server.ViewObjectImpl.associatedReferenceEntities(ViewObjectImpl.java:7697)
     at oracle.jbo.server.ViewRowSetImpl.initForeignKeyValues(ViewRowSetImpl.java:3206)
     at oracle.jbo.server.ViewRowSetImpl.initForeignKeyValues(ViewRowSetImpl.java:3166)
     at oracle.jbo.server.ViewObjectImpl.createInstance(ViewObjectImpl.java:2104)
     at oracle.jbo.server.QueryCollection.createRowWithEntities(QueryCollection.java:771)
     at oracle.jbo.server.ViewRowSetImpl.createRowWithEntities(ViewRowSetImpl.java:1438)
     at oracle.jbo.server.ViewRowSetImpl.doCreateAndInitRow(ViewRowSetImpl.java:1476)
     at oracle.jbo.server.ViewRowSetImpl.createRow(ViewRowSetImpl.java:1460)
     at oracle.jbo.server.ViewObjectImpl.createRow(ViewObjectImpl.java:5400)
     at com.ge.med.bone.ui.base.MappingPanel.addToAssigned(MappingPanel.java:273)
     at com.ge.med.bone.ui.base.MappingPanel$1.actionPerformed(MappingPanel.java:192)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
     at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:245)
     at java.awt.Component.processMouseEvent(Component.java:5100)
     at java.awt.Component.processEvent(Component.java:4897)
     at java.awt.Container.processEvent(Container.java:1569)
     at java.awt.Component.dispatchEventImpl(Component.java:3615)
     at java.awt.Container.dispatchEventImpl(Container.java:1627)
     at java.awt.Component.dispatchEvent(Component.java:3477)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
     at java.awt.Container.dispatchEventImpl(Container.java:1613)
     at java.awt.Window.dispatchEventImpl(Window.java:1606)
     at java.awt.Component.dispatchEvent(Component.java:3477)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)What could cause that exception? In 9.0.3.2 the code worked just fine. What's happening at line 3268 in ViewDefImpl?
Regards,
Sascha

I don't know. We have extended entities of course. But I don't think that this is related to the problem.
The editor takes always long to come up. Haven't seen an association yet, where it comes up quickly. Even if no extended entities are shown in the trees it takes long. This is at least my impression.
And this is really bad, because due to a new BC4J bug (??) we have to change lots of associations.
Sascha

BC4J bug in 9.0.3.3

Similar Messages

Maybe you are looking for