Theres nothing stopping you using a doc datasource in a custom control.

 

I'll need  more details like how are you trying to open the doc ? are you passing in a doc id? searching for one based on a key? etc.

 

 Hi Simon,

 

i've tried to test the access to the document with a statement like this:

 

<xp:label value="#{doc1.lang}" id="label1"></xp:label> 

 

On the Xpage (where the document is opened)   the field content  appears.

 

In the area of the emdedded CC there apears nothing in one case. 

But in case of a second CC  (on the same  Xpage)  the field content  appears also.

 

I can't see the difference ?? You mentioned something about passing parameters of the doc to the cc. 

 

How should i do this ? I want to prevent to open the doc again. Or is that necessary ?

 

Thanks 

Uwe 

 

Hi,

 

There is no difference in opening a domino doc in a custom control verses in an XPage. you defeine a data source and then you provide some means for it to query which document your interested in by:

If you are unsure how to deal with documents in XPages as a whole then you should look into some examples. There are templates that come with XPages that can be deployed, I've modernized 2 of them and they are currently on openNTF.org as part of the ExtLib project (Discussion / Teamroom). These would be good examples to look at and web sites like:

 

http://xpageswiki.com/web/youatnotes/wiki-xpages.nsf/dx/Work_with_documents_and_fields_on_the_XPage  

 To say it in short words: i have to open the datasource again in the CC. That's not great under performance aspects.

 

Thank you 

 

 no your not opening a document a second time. the datasource is a connection to the domino back end.  you have to provide it details of what it is ur looking for. the same way when using a JDBC connection you can't create one and ask for fied 1 of a result set before you do the query. 

 

without an id or a search of some kind a datasource is just a blank connection 

There are (at least) two ways to access a document data source from within a custom control:

 

 1) use the 'currentDocument' object. This should be all you need if there is only one document datasource in use on your xpage. If there is more than one document data source on your page, it will find the 'closest' document, by walking back up the control tree. If you need to control which doc datasource you really need to work with, use method 2. 

 

2)  You can pass the document datasource as a property of the custom control. You create a property with the type com.ibm.xsp.model.ModelDataSource (type it in, it doesn't show up as a choice), then pass your datasource as the value of that property where you instantiate your custom control. Then you access that datasource through the compositeData object in your custom control. In any javascript computation, I find is useful to define a local variable and cast it as a NotesXspDocument to get the advantages of type-ahead in the editor:

Rich 

 

I've tried method 2 and it worked !!

 

Thank you very much ..... 

Uwe