Need suggestions on a Bea Portal pattern

[Kruzer]

The Java pattern I was thinking of using would be JSP (portal), Tag Libs, Interface classes, DAO/Value objects.

Any other suggestions/changes?

Thanks!

Dano
dan_kryzer@hotmail.com
What's your major malfunction

 

[sedj]

For what ? A telnet web service ... or something else ?
Generally, the whole story is needed to provide advice !

BTW, please remove your email addr from your signature - it attracts spammers ...

--------------------------------------------------
Free Java/J2EE Database Connection Pooling Software

http://www.primrose.org.uk

 

[Kruzer]

The BEA portal application will be call center information website were about 12,000 users will be using this app for policies/ content viewing. I work for a content management company and I'm implementing the companies API into call center portal application. There is already an established process for accessing the repository through this API, but I need to pass the objects to the portal interface. I'm new to portlets and I'm looking for a Java pattern that someone has used in the past with portlets. What is a good approach to updating a portlet with out refreshing the overall interface, can this be done?

My initial thoughts were to build the portlets in the BEA workspace (JSP pages), create business delegates that provide the result set object, an interface layer at the Bea application scope, and Data Access objects that return records that do not access the repository. When the repository is called I will use the "companies" API which will have logic built into the interface layer.

Does this help describe the architecture?


Dano
What's your major malfunction