There are a number of posts in the forums looking for starter information. Don't worry. There are many resources out there that can be easily accessed online.
The first place to go is the application's documentation. It is a resource that should be each and every person's first line of defense. At least read through the table of contents before you start to code.
WebCenter Content Documentation Home:
http://www.oracle.com/technetwork/middleware/webcenter/content/documentation/index.html
The WebCenter community page also has dozens of resources that are publicly available:
http://www.oracle.com/technetwork/middleware/webcenter/content/community/index.html
A key asset is the 2006 "Definitive Guide to Stellent Content Server Development" written by Bex Huff: http://www.apress.com/9781590596845
And, a number of sample components can be found from the Downloads page:
http://www.oracle.com/technetwork/middleware/webcenter/content/index-092832.html
and, also on the "Sample Code" page:
http://www.oracle.com/technetwork/indexes/samplecode/webcenter-contentsamples-1352729.html
Each of those links can be found from the product's homepage on Oracle.com. There are many, many resources out there, but you're only going to get out of them what you put in!
The Oracle team and a number of people in the community (forums & blogs) have put a vast amount of information out there for everyone's reference and knowledge. All you have to do is search and absorb.
Once you've put some of your own time into your skill set, then the next step is putting together a forum post or support ticket. Each will be similar in content. You'll need to supply a basic amount of information so that others will have some idea of your situation (remember that we haven't been over your shoulder for the last 10 hours debugging with you! :) )
- Your basic environment (os, application version & build #, application server version, whether you're using a web server or any other application layers, database version and type, and any other pertinent information)
- Your requirement - what you're expecting the system to do
- Your Error - the error message, screenshots, full stack traces, etc
- Your Use-Case - how did you trigger the error. is it regular or is it random? do some cases work, but other fail? Was this working in the past, but recently stopped working?
Always error on the side of too much information.
I bet that there's at least a 50% chance that you'll uncover your own solution when you go through that last scan of due diligence!
The links and information above will send you on your journey.
Good luck!
-ryan
