Webconnector 3.10 api documentation and classes

I have a web connector in portal 7.4.2 configured and working but what I need to do is implement the

com.vignette.portlet.buildingblock.webconnector

.interpolator.RequestResponseInterpolator

I have had to copy the classes out of the web connector car into my development environment as well as out of the portal/webinf/lib so that I can compile.

The documentation is either difficult to find or does not describe what to do very well.

So Here are my questions.

1. Is there a better way of satisfying compile dependancies?.

2. Once I have written my class how and where do I bundle it and deploy it to the server.

3. Where do I find the API documentation?

Find more posts tagged with

Comments

Matthew_Hannay

I have found some documentation the Class needs to be bundled up in a CAR file. Thats fine.

I find it really frustrating that the documentation jumps all over the place and then you have to co hunting

for another referenced document. I have spent 10 minutes coding and 2 days trying to find doco and work out how to go about things!!

What I am nor struggling to work out is what the component .xml needs to look like especially the

component-type="" value and the contents of the <epideploy:detail></epideploy:detail>

parts of the file.

Matthew_Hannay

So I can find example code

https://knowledge.opentext.com/knowledge/cs.dll/wiki/17708023/WebConnector 3.0 Sample Code Package

But with out a component.xml as an example its pretty useless!!

Can Any one provide an example it a bit hard to create a car with out a component.xml

Gregory Guttmann

Hi Matthew - If you go into the bootstrap directory (something like /portal/system/bootstrap), there are all the CAR files that were deployed right after the portal was installed. You can unzip them to locate the component.xml files. Certainly not as good as proper docs, but very useful nevertheless.

Attached are some component.xml files - the first one is the WebConnector component.xml.

For other OpenText customers who are using Siterise, just add /portal/system/bootstrap as a resource and then you can transfer individual CARs to the resource library and then explore the CARs or extract individual elements like the component.xml.

Gregory thanks for the clarification.

For any one searching I have found a couple of things.

The PortalDevGuideLD1.pdf section 3 give more info on how to create and deploy a bean.

If you just need somthig to work quickly with out localisation the following works well. as a component.xml

<?xml version="1.0" encoding="UTF-8"?>
<epideploy:component build-version="1000004"
                     component-id="com.portal.MyModuleBean"
                     component-type="ModuleTypes"
                     description="bla bla"
                     epi-build="1"
                     epi-version="7.4"
                     major-version="7"
                     minor-version="4"
                     title="MyModuleBean"
                     xmlns:epideploy="http://www.epicentric.com/deployment">
<!-- If you have a dependancy put it here

<epideploy:required-component component-id="com.epicentric.module_component.XCMUtils" component-type="ModuleTypes" major-version="7" minor- version="4"/> -->
<epideploy:detail>
    <module-config auto-deploy="true">
      <descriptor-id>QDEXUserProxyFilter</descriptor-id>
      <web-deployment-path>/beans/qdexuserproxy</web-deployment-path>
      <locale-key/>
    </module-config>
</epideploy:detail>
</epideploy:component>

Matthew_Hannay

Sorry small typo in the epideploy:detal I missed moving out my real name as I was making it generic

<?xml version="1.0" encoding="UTF-8"?>
<epideploy:component build-version="1000004"
                     component-id="com.myportalco.MyModuleBean"
                     component-type="ModuleTypes"
                     description="bla bla"
                     epi-build="1"
                     epi-version="7.4"
                     major-version="7"
                     minor-version="4"
                     title="MyModuleBean"
                     xmlns:epideploy="http://www.epicentric.com/deployment">
<!-- If you have a dependancy put it here

<epideploy:required-component component-id="com.epicentric.module_component.XCMUtils" component-type="ModuleTypes" major-version="7" minor- version="4"/> -->
<epideploy:detail>
    <module-config auto-deploy="true">
      <descriptor-id>MyModuleBean</descriptor-id>
      <web-deployment-path>/beans/mymodulebean</web-deployment-path>
      <locale-key/>
    </module-config>
</epideploy:detail>
</epideploy:component>