I know that inline styles are generally a last resort, but I was trying to get something quick and clean up with the customer’s logo where it belonged and just could not get it to work. My inline attempt was to do the following:

<af:image source="/images/logo.png" 
          shortDesc="[customer] logo" id="pt_i1""/>

But that resulted in the image being stretched across the whole panel. Then I figured I would just add the size like this:

<af:image source="/images/logo.png" 
          shortDesc="[customer] logo" id="pt_i1"
          inlineStyle="width:159px; height:85px;"/>

But same result. While trying to figure things out, I added a space thus:

<af:image source="/images/logo.png" 
    shortDesc="[customer] logo" id="pt_i1"
    inlineStyle="width:159px; height:85px;"/>&nbsp;

And it worked! But, I did not want to rely on such a hack, so I looked and looked and looked and finally figured out how to had a simple custom class:

af|panelGroupLayout.pageTemplate_custDefaultPageHeader 
{
background-image:url('/oracle/webcenter/portalapp/shared/cust_Logo.png');
background-repeat: no-repeat;
}

Where af|panelGroupLayout is an existing ADF Faces selector, and applied it:

<af:panelGroupLayout layout="vertical"
   xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
   id="customDefaultBannerDiv" 
   styleClass="pageTemplate_custDefaultPageHeader"
   inlineStyle="margin-top:10px; min-height:98px; text-align:right;">

And everything was good. For now.

© Scott S. Nelson

I finally got around to installing the latest WebCenter and JDev today. I wasn’t quite ready to give up my old version, so I wanted an easy way to have both without any clashes.

The first step was to obviously choose a separate installation path. The less obvious piece was to set the

If you must have multiple versions installed, set the value of ide.user.dir.var to something other than the existing  JDEV_USER_DIR. This can be done my modifying [MIDDLEWARE_HOME]/jdeveloper/jdev/bin/jdev.boot and setting a new value there, then set a location for the new value. In my case, I used:

ide.user.dir.var = JDEV11.1.1.7_USER_HOME,JDEV11.1.1.7_USER_DIR

and set the environment variable:

JDEV11.1.1.7_USER_DIR=E:\JDEV11.1.1.7

I’m too lazy to put the environment variable screenshots here for those that need them, but someone already did at http://adfhowto.blogspot.com/2011/02/change-jdeveloper-system-directory.html

© Scott S. Nelson

I noted yesterday about Where to Put Your WebCenter Producer Connections that the process for making it an IDE connection still started in the Application panel. Now I know why. I added another portlet to the producer and it shows up in the IDE Connection resources but would not drag into the application. Leaving off a few hours of frustrated Googling, I eventually went to the connection in the Application resources and discovered that the Producer had to be refreshed there in order to make it available to the application. Other than a reference point, I don’t see the reason to even have in the IDE panel now that I see how it works.

© Scott S. Nelson

When creating a WSRP connection, the documentation says “For other methods of invoking the wizard, such as from the Resource Palette, see Section 1.6.2, “How Do I Access the Connection Wizards?” (64.2.1 How to Register a WSRP Portlet Producer) but in the case of WSRP producers, for both Resource Palette and Application Navigator, you invoke the wizard from the Application Navigator and then choose where the connection will be stored:

© Scott S. Nelson