The Incident Archive

When creating a EO for the table accross schemas always prefix your schema object with the schema name: ie common.table It is not enough to select the Database Schema from the drop down

http://xmlandmore.blogspot.com/2012/12/understanding-incident-and-diagnostic.html Really really helpful blog thanks Stanley.

NOTE: This may break some stuff so backup before you proceed so you have been warned Prerequisites: Install JDev 11.1.1.6 Run integrated weblogic. Now install just weblogic 10.3.6 I used the generic installer. java  -jar -D64 -Xmx1024M wls1036_generic.jar Next > Select Create new MiddlewareHome and enter a value > Next > Typical > Next Now select your JDK and click Next * 3 Run QuickStart Click Next Select 9.0 or Higher Click Next Find your integrated domain  [usually under C:\Users\[username]\AppData\Roaming\JDeveloper\system11.1.1.6.38.62.29\DefaultDomain] NOTE: On windows I had to make this folder ! read only but this is not recommended. If you don't want to do this Install your integrated server in a different location Click Next. Once the Installer has finished backup setDomainEnv.cmd then copy setDomainEnv.cmd.back to setDomainEnv.cmd and edit the line: set WL_HOME=... and make it set WL_HOME=C:\Dev\Oracle\Weblogic_10.3....

After a little holiday and a change of continents I am back to blogging. Hopefully I will have a few more Web Center and UCM posts also.

I had a showdetailheader inside a forEach which would just not disclose/ hide. No matter what I tried the header would just not work. So I changed the for each value from a binding to a get from the backing bean and everything worked as it should. Strange...

11.1.1.5 So here is my handy list to myself of things to check if you are getting weird problems with things that should work (buttons not work, or drop downs misbehaving): Mark you table as contentDelivery="immediate" Remove partialSubmit="true" from some buttons Remove immediate="true" from buttons Use af:forEach instead of af:iterator.

So I was playing around with generics (dont love them because of type erasure - class level is ok method level gets scary) the other day and here are some examples and lessons learned: 1) Method level generics with return types are harder than they look. 2) Wildcards and when to use them confuse me. 3) My code is ugly and I must be missing something but what - who knows. What I wanted was a Singleton class with generic get and put methods (what you put in is what you get out) without the cast. Something that works a little like Collections.emptyList(); The map I was storing my generic stuff in  ignore the naming for now: What I wanted to do is something like this: CacheItem<AnItem>  someCacheItem  = new DateCacheItemImpl<AnItem>(); Cache.getInstance().register(NameCacheItem.class); Cache.getInstance().put(someCacheItem); CacheItem<AnotherItem>  anotherCacheItem  = Cache.getInstance().get(); p...