Renan Monteiro's Sharepoint

Hi! Here are two ViewObjectImpl sample methods, one using direct Where Clause modification and another one using ViewCriteriaRow API: Class br.com.home.view.JobsVOImpl.getJobWithMinimumSalary() private static ADFLogger LOGGER = ADFLogger.createADFLogger(JobsVOImpl.class); private String minimumSalaryWhereClause = "MIN_SALARY IN (SELECT MIN(MIN_SALARY)\n" + " FROM HR.JOBS)\n" + " AND ROWNUM = 1"; private String minimumSalaryWhereClauseVC = "SELECT MIN(MIN_SALARY)\n" + " FROM HR.JOBS\n";     public String getJobWithMinimumSalary() {         setWhereClause(minimumSalaryWhereClause);         LOGGER.warning("WHERE clause -> " + this.getWhereClause());         executeQuery();         String jobId = "...

Morning! When running a task-flow as a dialog do not forget to add those attributes to the button that calls the btf: useWindow="true" windowHeight="400" windowWidth="500" Without this you'll probably run into a 404 error, here is part of the exception (pt-BR message): <XmlHttpServletResponse> <_logException> javax.servlet.ServletException: ADF_FACES-60101:Código de Status de Erro de HTTP: 404."

Just posting for future reference. I had a JBO-25030 today and its problem was associated to a Entity Assocation marked as "Composition", the problem is that new rows doesn't contain a default associated item. Eg: You create a product without its category and product category is a Composition Association from the Products table to the Product Categories table.

Hi all, Today I was working a lot only running the Application Module by itself. I had a View Object that I implemented its Java View Row Class. After some time I decided to change one attribute from "String" to "Number", running the AppModule again was giving me the exception: oracle.jbo.AttrValException: JBO-27019: The get method for attribute "attributeName" in "ViewObjectName" cannot be resolved. Bored of trying to solve the error I created a new VO based on the same EO. The new VO worked, so, I compared both of them (the new one and the old one), one difference of course is the RowImpl class, I implemented it on the new VO too moved my comparisons to the Java RowImpl class. This lead me to a strange IDE bug, after changing a Entity Attribute it does not refactor the ViewRowImpl class (I know it is too far for the IDE to know that kind of information but the fact is that it does not send us any intelligent messages about the error). ...