
	Where results make sense

Topic: JSR168

	Re: [wsrp-wsia] JSR168 & WSRP aligment
		When JSR168 EG decided to get rid of non-blocking action from the API one of the key arguments was that it could still be possible to model non-blocking actions by using getMarkup.
		JSR168 producer implementations could define extensions to expose WSRP properties metadata 6-------------------------------------------------------------------- JSR168 defines the concept of windowID to uniquely identify an occurrence of a portlet in a portal page.
		JSR168 producers would have to map the WSRP window state names to the JSR168 window state names on each performInteraction/ getMarkup.
	www.oasis-open.org /archives/wsrp-wsia/200210/msg00196.html (1228 words)

	FitzBlog : WSRP and JSR168 Are Two Completely Different Things...
		The fact that they’re uttered in the same breath is (a) a problem, and (b) no doubt fueled by some (not all) overzealous vendors who’d like you to believe you can’t have one without the other.
		JSR168 is a standard for how to code portlets in Java.
		Cross-Product: JSR168 portlets can, in theory, be written originally to be used in one vendor’s Java-based portal product but can be deployed in another vendor’s Java-based portal product later.
	blogs.msdn.com /mikefitz/archive/2006/02/10/529682.aspx (1199 words)

	DraftPortletsContent
		JSR168 mentions portlet filters as a feature which will be defined in the next specification.
		JSR168 leaves the method of communication between portlets to the next specification, so there is currently no official API through which portlets can send messages to each other.
		With JSR168, there is no way for a portlet to access these services: it cannot inspect its page environment or other portlets, and security is limited to the PortletRequest functions getUserPrincipal/getRemoteUser and isUserInRole.
	www.doc.ic.ac.uk /~mo197/portlets/docs/draft_limitations.html (3987 words)

	subbu.org: Portlets and Ajax - How Complete are the Standards?
		JSR168 and WSRP 1.0 provide for three kinds of URLs that portlets can create in their markup.
		In both JSR168 and WSRP 1.0, if you want a portlet to process a request, the URL used to submit the request must either be a render URL or an action URL.
		To restate, the key limitation with JSR168 and WSRP 1.0 is lack of sematics to allow portlet's response to be returned directly to browsers without page aggregation.
	www.subbu.org /weblogs/main/2006/02/portlets_and_aj.html (1265 words)

	Enterprise Portal, Portlets, JSR168: July 2005
		As portlets are built over servlets it has all the basic features of servlets like Multi-Threaded, Procedure of Loading Class loaders, Request and Response semantics are also similar.
		The sequence is shown in above diagram(from JSR168 specification doc).
		JSR168 allows three modes that is view, help and edit.
	portlets-jsr168.blogspot.com /2005_07_01_portlets-jsr168_archive.html (1717 words)

	Portlets - uPortal - JA-SIG Wiki
		WSRP was developed in collaboration with JSR168 but in itself is not Java specific.
		JSR168 portlets need to reside on the same application server instance (e.g.
		uPortal 3.0 is also being developed as the adhesive for the components of the SAKAI project, one of the aims of this project is to be JSR168 specification compliant.
	www.ja-sig.org /wiki/display/UPC/Portlets (630 words)

	JSR168Portlet - Cocoon Wiki
		JSR168 defines API for writing portable (across portal implementations) portlets in Java, and is similar (and related) to the Servlets spec.
		To implement JSR168 Portlet using Cocoon, JSR168 Environment is introduced.
		JSR168 environment for Cocoon maps Portlet primitives onto Cocoon primitives.
	wiki.apache.org /cocoon/JSR168Portlet (275 words)

	Office of Information Technology
		Its long term strategy is to adopt JSR168 only to allow incoming channels, not to allow its content to be deployed elsewhere.
		Sometime in the future, especially if it adopts the new JSR168 and WSRP standards much more quickly than other portals, it may be a viable enterprise portal for Princeton.
		JSR168, commonly called a “portlet” standard, will enable a channel that is developed anywhere to be run in any framework that supports the standard.
	web.princeton.edu /sites/oitteams/itateam/portal.htm (2520 words)

	Chapter 1. JSR168 portlets (Site not responding. Last check: 2007-11-03)
		The JSR 168 specification aims at defining porlets that can be used by any JSR168 portlet container also called portals.
		As of today, JBoss portal is fully JSR168 1.0 compliant, that means that any JSR168 portlet will behave as it should inside the portal.
		What is really important to know about such portlets is that when a page is displayed it is divided into two distincts parts, an action part on one portlet followed by rendering parts for every porlets displayed on a page.
	docs.jboss.org /jbportal/v2.0RC/reference-guide/en/html/jsr168.html (245 words)

	Thesis Chapters (Site not responding. Last check: 2007-11-03)
		For comparison, we consider JSR168 primarily in the context of Java web server technologies, the core of which is J2EE and Java Servlets, but which also includes non-JSR168 Java portals.
		JSR168 leaves the method of communication between portlets to be defined in the next specification, so there is currently no official API through which portlets can exchange messages.
		With JSR168, there is no way for a portlet to access these services: it cannot inspect its page environment or other portlets, and security is limited to the
	wwwhomes.doc.ic.ac.uk /~mo197/portlets/thesis/portlets.php (4160 words)

	[wsrp-wsia] WSRP conf call on JSR168-WSRP aligment
		Dear WSRP TC and JSR168 EG, This email is being sent to the WSRP TC and JSR168* EG aliases* Following is a brief summary of today's WSRP conference call on WSRP-JSR168 alignment.
		WSRP has asked for a use case where this info is required by the consumer.
		JSR168 EG will consider making a recommendation on user-info attribute names in the portlet spec.
	www.oasis-open.org /archives/wsrp-wsia/200210/msg00283.html (438 words)

	Forum .LRN Q&A: dotLRN Portal Framework and uPortal
		I notice the Sun announcement says JSR168 will be incorporated (at the conference last summer the developers said they had no plans to look at JSR168).
		We had shelved it to see how JSR168 got on at Jetspeed (Jakarta Project) and CHEF (UMichigan) because we felt JSR168 was likely to get widespread industry adoption and a Java portal development that ignored it was driving up a blind alley.
		The JSR168 specification is due to be adopted in uPortal, but should also work in IBM, Sun, Oracle and Jakarta Jetspeed portals.
	openacs.org /forums/message-view?message_id=72972 (925 words)

	Java Competence Centre LogicaCMG » Standards like JSR168 and JSR127 make your life easy, or ….
		Standards like JSR168 and JSR127 make your life easy, or ….
		The next step should be easy we need to create a rich JSR168 portlet application using JSF technology.
		After that we can just create a war-file which will be automatically deployed by Jetspeed.How wrong can one be, standards are not their to work with each other out of the box one must create a bridge for these two standards to work together.
	www.bloggingaboutjava.org /cms/wordpress/2006/05/standards-like-jsr168-and-jsr127-make-your-life-easy-or (813 words)

	JSR168/WSRP Environment
		The JSR168 portlet is deployed such that it is accessible within a local installation of uPortal.
		The JSR168 is also deployed within the WSRP4J producer, this allows the JSR168 portlet to be access via WSRP either from a local or remote uPortal installation
		The reason for this step beyond normal war deployment is that the portlet-guid in web.xml needs to be set to {context}.{servlet} where {context} is the portlet's servlet context, and {servlet} is the portlet's servlet mapping.
	www.oucs.ox.ac.uk /portal/developers/environment.xml?style=printable (694 words)

	MVC WebWork Portlet Framework
		WWPortlet is a MVC Framework for JSR168 Portlet based on WebWork,Velocity, Spring, Hibernate.
		Recently more & more developers are interesting in Portal Development, but JSR168 API is difficult to learn to develop big reality application.
		Also JSR168 API is different from traditional Servlet API, every client post request is seperated to two steps to run: processAction, (doViewdoHelpdoEdit).
	wwportlet.sourceforge.net (357 words)

	Portlet - Wikipedia, the free encyclopedia
		The Java Portlet Specification (JSR168) enables interoperability for portlets between different web portals.
		This specification defines a set of APIs for interaction between the portlet container and the portlet addressing the areas of personalization, presentation and security.
		Apache Pluto is a reference implementation of JSR168.
	en.wikipedia.org /wiki/Portlets (327 words)

	jsr168 - SWiK
		The contents of jsr168 page and all pages directly attached to jsr168 will be erased.
		Ajax portal portlet jsr168 jsr-170 jsr170 JCR … Dec 02
		J2EE Java LDAP CMS jsr168 jsr-170 jsr170 opensource activedirectory … Nov 22
	swik.net /jsr168 (435 words)

	Description
		L'objectif du projet pict est de créer un moteur de portail conforme à la norme jsr168 et capable de s'adapter élégamment à un maximum de situations.
		pict est une implémentation complète d'un moteur de portail jsr168.
		La norme jsr168 est une spécification qui standardise les développements de portlets et portail J2EE.
	www.p-i-c-t.org /presentation/description (576 words)

	Get Ready for Fourth-Generation Portal Technology
		The emergence of portlet standards — Web Services for Remote Portlets (WSRP) and Java Specification Request 168 (JSR168) — in 2H03 will provide a key component of generation-four portal functionality, but won't immediately provide the required level of interoperability (see "The JSR168 Standard: Underpowered vs. Just Right").
		Until a more-complete set of interoperability standards emerges to allow seamless portal federation, a tactical approach must be taken.
		"The JSR168 Standard: Underpowered vs. Just Right" — JSR168 holds great appeal in terms of its potential ability to heal fragmentation in the portal market.
	www.gartner.com /DisplayDocument?id=410459 (1026 words)

	java marcher
		Right now there is a huge momentum around JSR 168 portlet development environment in the Open Source World.
		When your portlet is OK, just switch the RunTime target to JES-Portal 7 to integrate the portlet into your portal.
		This portlet project has been tested with Glassfish/OpenSource JSR168 Portlet Container and JES-Portal7.
	blogs.sun.com /patriceg/entry/you_can_deploy_jsr168_portlet (244 words)

	Bookmarks Portlet
		This JSR168 compatible portlet bookmarks application is based around the XML Bookmark Exchange Language (XBEL) format.
		It was initially targeted at the uPortal platform but should work in any JSR168 container.
		Originally developed as a standalone application, it has been converted to a JSR168 portlet through the use of the Struts Bridge from the Apache Portals Bridges project.
	bmarks-portlet.sourceforge.net (459 words)

	Jive Software Support: Portletize jive forums ...
		Actually, it would be GREAT if Jive Forums could support the JSR168 Portlet Spec.
		This would allow Jive to easily plug into any portal application server which implemented the JSR168 specification for portlets.
		TIBCO's PortalBuilder 5.x coming out this year will support JSR168 and I believe there are several other portal application servers which currently support it as well.
	www.jivesoftware.com /jive/message.jspa?messageID=99467 (244 words)

	Portlets Repository (Site not responding. Last check: 2007-11-03)
		Warning: Most of these "portlets" are not JSR168 compliant yet.
		All the "portlets" developed by Jahia Solutions are available under the CDDL open source license.
		Two different versions of the portlet exist: one servlet based for Jahia 4.0 or 4.1 releases and one JSR168 for Jahia 4.5+.
	www.jahia.net /jahia/571 (1867 words)

	The JSR168 Standard: Underpowered vs. Just Right
		The portal market has many needs that a complete and comprehensive portlet standard could potentially address.
		JSR168 is not such a standard but will, nevertheless, serve as the most important of various portal-related standards.
		Purchasing this document is fast, easy and secure, but you must be registered with gartner.com so we can track your order.
	www.gartner.com /DisplayDocument?doc_cd=117455 (220 words)

	Roseindia.net- JSR168 - Open Source JSR 168 Portlet Factory (Site not responding. Last check: 2007-11-03)
		Add your tutorial to our Java Resource and get tons of hits.
		JSR168 - Open Source JSR 168 Portlet Factory
		IT managers are continually asked to do more with less.
	www.roseindia.net /search/tutorialdetails.php?id=6511 (240 words)

	Pragma (Site not responding. Last check: 2007-11-03)
		I have been tinkering with a couple of the free and open source JSR168 (portlet specification) compliant portals out there and have met nothing but frustration and failure.
		I really want to get started developing JSR168 compliant portlets but cannot find a platform to start working with.
		I guess this is one of the disadvantages of being at the mercy of free or open source projects.
	www.jroller.com /page/ericrobe/20040606 (1312 words)

	JSR168 support with WSRP- good or bad?
		We've even had customers write PHP-apps specifically intended for consumption by the proxy portlet, which is very neat and tidy, and the customer gets to develop his app in any way he sees fit.
		The long term goals we have for integration is indeed to use WSRP to integrate with all apps.
		This is similar to the idea I had about wrapping existing apps with a WSRP proxy producer, except that it is a Java-only variant, which has its perks (performance being one of them).
	www.theserverside.com /news/thread.tss?thread_id=39077 (7099 words)

	JBoss.com - Forums - Seam JSR168 Portlet and EJB3 and Facelets
		Is it possible to develop jsr168 portlet with Seam using EJB3 and Facelets?
		I too would be very interested in seeing an example of this.
		I've prepared an Eclipse project, with JBoss IDE Packaging configuration for an EAR file that deploys a portlet instance of the "Guess a Number" sample application from the jboss seam source.
	www.jboss.com /index.html?module=bb&op=viewtopic&p=3942956 (879 words)

	subbu.org: Is the Portlet Programming Model Broken?
		In essence, such a redirect step would convert an unsafe interaction to a "safe interaction" that is safe to navigate, is repeatable, cacheable, and bookmarkable.
		The life cycle has two distinct phases (a) an action processing phase to make state changes, and (b) a render phase to render the current representation of a portlet.
		In the case of portlets, it is the responsibility of the portal or more accurately the aggregating app to redirect after POST.
	www.subbu.org /weblogs/main/2006/06/is_the_portlet.html (1340 words)

	Cooperative Portlets using JSF and JSR168 (Site not responding. Last check: 2007-11-03)
		Just as lo ng as the portlets follow JSF and JSR168.
		I've also tried to turn on tracing on the propertybroker, but it deos not lo g very much, even if I run the working example referenced above.
		Just as long as the portlets follow JSF and JSR168.
	www.webservertalk.com /message1453858.html (556 words)

	Introduction to JSR 168 - The Portlet Specification
		Available through the following links are FREE downloads of the Sun ONE Portlet Builder tool, a technical white paper, sample portlet code, prebuilt portlets, and access to the specification itself.
		Introduction to JSR168 -The Java Portlet Specification (pdf)
		This technical white paper provides an overview of the JSR 168 specification, outlines its benefits, details how it works, and includes sample code.
	developers.sun.com /prodtech/portalserver/reference/techart/jsr168 (778 words)

Try your search on: Qwika (all wikis)