Get the real story via our monthly newsletter

Search

    2
    0

rss

Send to a colleague

Home > Commentary > Trends Archive > Sun blog discloses issue with major portal release

Browse TrendWatch Blog

Recent Blog Entries

The Complete Archive

Trends by Vendor


TrendWatch by Channel

Web Content Management Trends

Enterprise Portals Trends

ECM Trends

Web Analytics Trends

Enterprise Search Trends

SharePoint Trends

Digital & Media Asset Management Trends

XML & Component Content Management Trends

E-mail Archiving & Management Trends


Report Excerpt

The Enterprise Portals Report 2009 looks at... Integration with office tools in Sun's Portal Server

"There is unfortunately no WebDAV support nor integration from within Microsoft Office of StarOffice. So, you can drop desktop files into the repository, but you cannot save directly to SJSPS from which your usual Office applications. "

(p. 264)

More about The Enterprise Portals Report 2009

Our customers say

"Every organisation considering portal technology should obtain a copy of the Enterprise Portals Report, to gain access to best-practice approaches and concepts, built up from real-world experience.
- - James Robertson,
Managing Director, Step Two Designs

NEW at CMS Watch

The Web CMS Report 2009 The Web CMS Report 2009: In its 15th edition, this report evaluates 42 web content management systems and vendors... Read more
The ECM Suites Report 2009 The ECM Suites Report 2009: This report evaluates 30 ECM offerings... Read more
Technology Transfer in Rome Join us in Rome: On November 6-7 in Rome, CMS Watch's Theresa Regli will teach a tutorial on "Enterprise Search Technology and How to Optimize It"... Read more

 

TrendWatch Blog

Sun blog discloses issue with major portal release

10-Apr-2006

In late 2005, Sun announced version 7.0 of its portal platform. As with all new major software releases a few problems have been identified. Keeping inline with the "Web 2.0" focus of the release, a Sun employee recently blogged about a reasonably significant bug regarding portlet errors. The blog posting nicely documents some work-arounds to the problem. This communications approach is a welcome departure from the usual norm, where vendors only acknowledge issues late in the process and rarely document them well.

- Submitted by: Janus Boye, Contributing Analyst

All Portal Channel Trends

Join the conversation

Digg This! Search Technorati Tag it on Del.icio.us



Get a Free Sample

Wondering about CMS Watch research? Sign up to receive free samples of any of our products.




What we do

CMS Watch™ evaluates content-oriented technologies, publishing head-to-head comparative reviews of leading solutions. What makes us special?

  • Our critical analysis exposes product weaknesses as well as strengths
  • We deliver unrivaled technical depth and comprehensive project advice
  • Our research is led by international topic experts
  • We only work for buyers -- never for vendors

Contact us

CMS Watch

info@cmswatch.com

18113 Town Center Drive, Ste 217

Olney, MD USA 20832

1 800 325 6190 (customer service)

+1 617 763 5336 (int'l customer service)

Fax: +1 214 242 3048