Renan Monteiro's Sharepoint

This error usually happens when you forgot to declare the Tag Libraries in your Web project inside JDeveloper, just import the library (trough JSP Tag Libraries inside your IDE, I'm using JDeveloper here but I think that all of then uses the same concept) that references the attribute TAG and everything should compile.

In day-to-day use JDeveloper always make some weird things by itself... Here I'am showing how to solve the most common one, the Data Control Palette got hidden somewhere in the darkness... Screen showing the Palette: Altough I was not able to reproduce the problem I know how to solve it, you just have to go to Window Menu and click "Reset Windows to Factory Settings", that'll fix some lost tag in one of JDeveloper configuration XML's.

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). ...

Hi all! I was facing some issues with this new Jdeveloper release (11.1.2) also called a "SHERMAN" release. The problem seldom appears but probably did some developers to reinstall the tool. Here is a sreen of the bug in all of its glory: This bug usually occurs when something is wrong with your web project in particular, but when I looked into other projects it was happening to everything loaded with Jdeveloper, so this is not a project-specific bug. After some time working out with Jdev user directory (here I find it under C:\Documents and Settings\MY_WINDOWS_USER_NAME\Dados de aplicativos\JDeveloper\system11.1.2.0.38.60.17), deleting and moving directorys around I released that a specific directory was giving the issue, its name is "o.j2ee.jsplib" . Looks like this directory store some information about libs that IDE uses to visualize JSF components, like taglibs or something else. You just have to delete this directory and let Jdeveloper ...

There is a know error while using Data Controls with the same name as packages like same minutes ago this ocurred to me: My package is named xpto.jobhistory and the entity is named JobHistory (case insensitive bug), by default my Entity Data Control reference was named with JobHistory.xml. This situation lead me to a bug when running the .jspx page, these JBO-25080. Hope it helps!