PropertyManager for the Content

Question

Hi all,
How can we define the PropertyManager for the Content Property ?
I mean the values for the property of a content in the Repository will come
from an external Data source.
And we want to manage these property values separately in our application.
Can we use EntityPropertyManager for the content. But in the documentation
its given for the User and Groups.
Thanks,
Karthi.

Answer 1

You can always try the JavaDoc:
http://e-docs.bea.com/wlp/docs81/javadoc/index.html
Pay particular attention to the com.bea.content,
com.bea.content.expression (for implementing search), and
com.bea.content.spi packages.
You will need to implement a com.bea.content.spi.Repository which
returns Tickets which return your implementations of
com.bea.content.spi.NodeOps, ObjectClassOps, and SearchOps. For search,
also be sure to look at com.bea.content.expression.Search and
ExpressionHelper for more details about what the search expressions look
like and what the standard properties should map to. Your implementation
classes shouldn't need to worry too much about caching since the
com.bea.content.manager framework should take care of caching.
You can put your jar in APP-INF/lib of the application to have it picked
up by the server, if your implementation doesn't include any EJBs
(because then you could just put it in the EJB jar file). You should be
able to write your implementation code in Workshop in a Java and/or EJB
project, since a Java project builds to APP-INF/lib and an EJB project
generates and registers and EJB jar.
You will need to register your Repository implementation in the
META-INF/application-config.xml file (or via the admin portal Server
screens).
Greg
Karthi wrote:
Alex,
The documentation you referred does not say any thing about how to use
content SPI.
But I hope this page...
"Content Repositories provide the storage mechanism for content, and they
comprise the second-level of the Virtual Content Repository hierarchy.
Content Repositories may include multiple instances of BEA repositories, 3rd
party repositories, or customer repositories. To plug into the Virtual
Content Repository, you must implement the BEA Content Management Service
Provider Interface - the CM SPI. "
http://e-docs.bea.com/wlp/docs81/contentspi/index.html .. where is the page
Sorry to say, this is improper.
Since the release of 8.1 Portal there is not correct documentation available
at correct.
Its horrible to think for a company like BEA.
Hope to hear Soon.
Karthi.
"alex toussaint" <[email protected]> wrote in message
news:[email protected]...
Hi,
The Portal CM system does not use the propertyManager. This is part ofUnified
User Profile - UUP:
http://dev2dev.bea.com/codelibrary/code/uup81.jsp
You can map external data sources, repositories, via the CM SPI andtherefore
manage external properties.
http://e-docs.bea.com/wlp/docs81/adminportal/help/CM_OV.html
--alex
"Karthi" <[email protected]> wrote:
Hi all,
How can we define the PropertyManager for the Content Property ?
I mean the values for the property of a content in the Repository will
come
from an external Data source.
And we want to manage these property values separately in our
application.
Can we use EntityPropertyManager for the content. But in thedocumentation
its given for the User and Groups.
Thanks,
Karthi.