Introducing the Portlet Specification, Part 1 With the emergence of an increasing number of enterprise portals, various vendors have created different APIs for portal components, called portlets. This variety of incompatible interfaces generates problems for application providers, portal customers, and portal server vendors. To overcome these problems, JSR (Java Specification Request) 168, the Portlet Specification, was started to provide interoperability between portlets and portals. Featured Resource
Extend the power of JSP with JSTL
Understanding Where to Install the ODI Standalone AgentWith no middle tier required in the ODI architecture, the most common question from people who are new to ODI is where to install the standalone agent: source, target or middle tier systems? Read this post by Fusion Middleware architect Christophe Dupupet for a look at possible architectures and recommendations for best choices.posted Mon, 14 Apr 2014 15:41:35 +0000 WC Sites Groovy Wrapper CSElement Example"By joining the URI of the page and the value from the ORA_FLEX_CACHE_KEY cookie we can create a flexible cache key that Akamai can use," says Michael Sullivan. "Akamai can then cache many versions of the same URI thereby offloading traffic to Akamai rather than having it coming back to Oracle’s servers."posted Thu, 10 Apr 2014 13:37:48 +0000
Oracle Oracle Oracle Technology Network > Java Challenge Win A Trip to JavaOne 2014 Build an application for the Internet of Things (IoT) Developer Challenge for a trip for you and two other team members to win a trip to JavaOne.