I hope to update this post with a vastly simplified approach to using the content presentation feature. Meanwhile, I do want to point out one thing that had me spinning my time for awhile. The URI for the templates TLDs in the sample files cause a compile error. At first I thought it was because the URI changed from http://www.bea.com/servers/content/ui/jsp/templates to http://www.bea.com/tags/wlpapps/contentui/templates, so I changed it. Then I got run-time errors because some of the methods aren’t in the new library. So I rolled back to the original values and just turned off validation for JSPs. That worked. So I am taking the approach of putting the templates into a shared library and taking the deployment hit rather than the development hit of having validations turned off for the main branch of the project. Later, I should create a build file that merges the projects at build time and drops the share library reference.
WebLogic Portal
WebLogic Shared Library Reference
One of those items I always have to go look up the specifics for is creating the MANIFEST.MF file for WebLogic shared libraries.
Reference URL can be found here.
Extra Required Step When Creating 10.3.2 WLP EAR
Wasted a good week until someone pointed out that OPOE does generates application.xml for exploded deployments (such as within the IDE) , but leaves it out when creating an EAR. So, when you create your WLP EAR project, you must check the “Generate application.xml deployment descriptor” box or the Portal Admin Tools will not get configured properly for the application.
Example of Creating a User in Oracle DB for WebLogic
One of those things I ran across recently that I always forget between projects so I thought I would share here:
1 Set the Oracle Home
export ORACLE_HOME=/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/
2 SQL Plus – Idle Instance $ORACLE_HOME/bin/sqlplus /nolog
3 Connect as SYS User
connect sys/welcome1@xe as sysdba;
4 Create the WEBLOGIC_PORTAL
User CREATE USER WEBLOGIC_PORTAL IDENTIFIED BY WEBLOGIC1;
5 Grant Roles and Permissions
GRANT CONNECT, RESOURCE,DBA TO WEBLOGIC_PORTAL;
6 The WLS install seems to expect a table named SYSTABLES, so you will need to create it:
CREATE TABLE SYSTABLES (TEMP NUMBER);
Creating a Local WLS 10.3.2 Domain
While setting up a new project this morning I was reminded of a somewhat counter-intuitive sequence when setting up a local environment (even with the simple Pointbase install). When you get to this screen:
Clicking Next will give you this warning:
Just click OK. The database isn’t running at this time.
And, for those who haven’t upgraded in a while and don’t read the manual, you will want to click Run Scripts when you see this screen:
After the wizard completes, look for the create_db.cmd in the domain root and run it before starting the server. The first start, the server will have problems starting. Let it run until nothing is spit into the console anymore, then kill it and start it again. This time it should come up.