StackOverflowError after adding a table to a TopLink Map

Question

Hello,
I am really puzzled by the next problem. After adding a table (Customer) to an existing TopLink Map, I get the same kind of error for every query in the project that I use.
ERROR J2EE EJB8006 [CustomerToplinkTestPublicFacade:public java.util.List com.companyname.toplinktest.model.CustomerToplinkTestPublicFacadeBean.findCustomersByCompany(java.lang.String,java.lang.String)] exception occurred during method invocation: javax.ejb.EJBException: java.lang.StackOverflowError
I get this with every page and every query, just change the name “findCustomersByCompany” to the name of the named query. Otherwise all pages seems to have the correct behaviour Removing the Customer-table from the application solved all problems, and they reoccurred after adding the table again.
I have no clue why this happens, the only thing that might be useful is the fact that the Customer-table is also a part of a database view which I already use.
… but why would that cause errors on queries it has absolutely no relation to…
Kind regards,
Nemata

Answer 1

hello,
another update on my testcases. I have used the following procedure to narrow down the source of the problem.
First I create one or more TopLink pojo's based on my database tables and views, add them to a session bean and create the data controls. I'm always working with the default named queries (selectAll).
Then I create a .jspx file, drag and drop a data control from the data control palette to create an ADF table with the defaults...
and run... with one of two outcomes.
I either get all the data from the table (correct) or I get a message "no rows yet" and an error message in the log window "2006-05-04 12:37:40.214 ERROR J2EE EJB8006 [testCustomerSession:public java.util.List model.testCustomerSessionBean.findAllCompany()] exception occurred during method invocation: javax.ejb.EJBException: java.lang.StackOverflowError"
This is an overview of the testing I have done:
Objects created | ADF table | Error
Customer | Customer | Yes
Company | Company | No
Customer and Company | Company | Yes
Company and ViewOfCustomer | Company | No
Company and ViewOfCustomer | ViewOfCustomer | No
Company and Person | Company | No
ViewOfCustomer is a database view with the same data as the Customer. So the table Customer seems to cause the problem.
Does anybody have an idea why a database table might cause such distinct problems ?
Kind regards,
Nemata