Connectors and MVC

OK, i have created simple connector like "Hello, world!". I see code, all are in content.jsp file.
I understood that i can put there what i want, for example, some Java bean to access Worksite API.

This is fine, but i need something more. In real i want to create kind of "portlet" based on MVC architecture.
It means i want to create real web application that will carry about my web.xml file as config file, servlet as controller role, Java beans as logic role, jsp as any presentation level.
I need some interaction with user as well by UI, because i need analyze coming parameters, do something then be back
at the some workspace but with different portlet view (for example, go inside current folder, or something).

So the first and important question
1) Are connectors good way to do this? If so, do we have some documentation about this kind of development and integration.
2) If not, what is the way to do it?

Thank you very much. I was tried to find some docs by search but didn't find something really useful.

Edited by Ort618 on 03/09/05 08:41 AM (server time).

Find more posts tagged with

Comments

peter_choe

I am trying the same thing. I created a servlet that will handle the request from the connector and forward the request to the appropriate jsp files. So, I was able to follow the MVC model using the servlet as the controller, getting configuration from the web.xml or any other xml files, and using the jsp for the presentation, and the java bean for the data or model.

The only problem I am having is getting a consistent behavior for the AppSession that is passed to the servlet to look up library and workspace information.

yuvpurush

Can anybody reply to this please. Even im also in the same situation. Response is appreciated.

JTNeville

There isn't a lot of documentatino on connectors but basically connectors are Interwovens way of giving you a consistent framework for you to talk to the MP services. Using the WOM and your language of choice, you can do mostly anything that is within the scope of the WOM (if you require MP interactivity) or some other service. Any self contained piece of code will work froma snippet, to a servlet to a full blown web application.

Take for example (please someone tell me what I did wrong in a apst life) our users often have trouble downloading the first few times. So I used MS's Windows Media SDK to create a custom media player connector. This allows the workspace manager to stick the connector media player into a workspace and at that time select from a list of asx file which content they want to show the end user.

The reason I used a connector is to offload the asx selection part from an IT admin onto a workspace creator. The connecotr framework lets you predefine the choices of your module and allow the workspace manager or workspace client to personalize a generic application. It also alllows me to track it's use within MP instead of just as statistics off my media server.

I'm not familiar with MVC but I'm sure Peter can give you more pertinent advice on that specific subject as he had already dabbled in that direction.