JSR 170 specifies a standard API to access content repositories in Java independently of implementation - see http://jcp.org/aboutJava/communityprocess/final/jsr170/index.html. JSR 168 is the portal spec, revolves around portlets - if you write a portlet based on JSR 168 you would get interoperability between portlet containers offered by different vendors - see http://jcp.org/aboutJava/communityprocess/final/jsr170/index.html

As you can see both are different.I see Magnolia Web content management system a Web CMS that supports JSR 170, so in future e.g if you wanted to move from one content repository, e.g database to a filesystem you could. I dont see it as a portal, it doesnt support JSR 168, doesnt provide a portlet container etc. A good example of open source portal offering is liferay, www.liferay.com

Typically in most web application projects this is a crucial architecture decision to be made, ie do you need a portal based system, web cms or both. Both of them focus on the presentation layer, Web CMS's focus more on the content and its lifecycle. In addition something like magnolia offers support for JSR 170 so your implementation is not locked to one underlying content repository.

vivek


----- Original Message ----- From: "James Frankman" <[email protected]>
To: <[email protected]>
Sent: Saturday, October 15, 2005 2:15 AM
Subject: [magnolia-user] JSR 168 vs. JSR 170


Can anyone explain the difference between the CMS specification JSR 170 and the Portlet specification JSR 168? Could Magnolia be considered a Portal? If so, is it compliant with JSR 168?

Any links or suggested reading material would be appreciated.

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------



----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to